From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1605 invoked by alias); 15 Mar 2012 09:32:52 -0000 Received: (qmail 1596 invoked by uid 22791); 15 Mar 2012 09:32:51 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 15 Mar 2012 09:32:16 +0000 Received: from nat-dem.mentorg.com ([195.212.93.2] helo=eu2-mail.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1S872d-0000w9-NZ from Thomas_Schwinge@mentor.com ; Thu, 15 Mar 2012 02:32:15 -0700 Received: from feldtkeller.schwinge.homeip.net ([172.30.64.227]) by eu2-mail.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 15 Mar 2012 10:32:14 +0100 From: Thomas Schwinge To: Jan Kratochvil Cc: gdb-patches@sourceware.org Subject: Re: [testuite patch] Fix cross-arch .S testsuite files compatibility In-Reply-To: <20120315090602.GA7079@host2.jankratochvil.net> References: <20120314201849.GB1412@host2.jankratochvil.net> <87aa3ikzrs.fsf@schwinge.name> <20120315090602.GA7079@host2.jankratochvil.net> User-Agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.3.1 (x86_64-pc-linux-gnu) Date: Thu, 15 Mar 2012 09:32:00 -0000 Message-ID: <8762e6ky5l.fsf@schwinge.name> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-03/txt/msg00526.txt.bz2 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-length: 1413 Hi! On Thu, 15 Mar 2012 10:06:02 +0100, Jan Kratochvil wrote: > On Thu, 15 Mar 2012 09:57:11 +0100, Thomas Schwinge wrote: > > In my patch I had explicitly taken care to replace .long with .4byte on= ly > > in .debug_* sections (and only in files that are not x86-specific, as it > > doesn't matter for those). You're now proposing such changes, too: >=20 > I checked specifically the "v" case where .debug_info already expects it = takes > _4_ bytes: > .byte 0x4 /* DW_AT_byte_size */ >=20 > It is true I did not check other cases but: >=20 >=20 > > I just wanted to check whether we can be sure that .4byte always conveys > > the same meaning as .long did in such cases? >=20 > as these testfiles were created on x86* .long is compiled there as .4byte. > This means that any such occurence of .long can be replaced by .4byte. >=20 >=20 > > Can there be other semantic differences between the two? >=20 > It is a good question and I am not aware of any such differences. Hmm, I just had a quick look, and found that, for example, tc-arm.c has this: #ifdef OBJ_ELF { "word", s_arm_elf_cons, 4 }, { "long", s_arm_elf_cons, 4 }, ... and obj-elf.c: {"4byte", cons, 4}, Compared to cons, s_arm_elf_cons does quite a lot of things, for example handle mapping symbols (which cons doesn't do, I think?). Gr=C3=BC=C3=9Fe, Thomas --=-=-= Content-Type: application/pgp-signature Content-length: 489 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJPYbcXAAoJENuKOtuXzphJMa0H/R2wM89v7AGzcI2gIvc/aev/ e24lWO85lAFfdFbAunPptF3mDI0fsGZ+Vi2AMQwXfB6DIYDZ1O7Yqhvv4+nAJ6Rb 8rF2cp2bts4Gs2QvqQL3M4g5IWPNWpuQ3i7Ccbfg8++39UxKk0h5guJTHV5wK3xe ZJsl/F0oC5Nk6meK1MSrTHVE2X6Xr5aL4yVUjQYSjtXe+pqL9p49v8/g3putwHmS vRUqyihObFS24c5fwAE9mwoLcMFyPOOmwczpEcEjXPP9OgHmSyWO99Lov/Z3/fhR ijxj4XdkxXSy1spMPCylitDHAKqKUKoeEGG+n96KdakVdUuBl41glVdBp5kp7uM= =mbSS -----END PGP SIGNATURE----- --=-=-=--