public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/6522: Incorrect struct offset for unaligned 64-bit fields in debug information
Date: Thu, 02 May 2002 18:42:00 -0000	[thread overview]
Message-ID: <20020503013602.30131.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/6522; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: jakub@gcc.gnu.org, fred@nextnewgig.com, gcc-bugs@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: target/6522: Incorrect struct offset for unaligned 64-bit fields in debug information
Date: Thu, 2 May 2002 21:32:08 -0400

 On Tue, Apr 30, 2002 at 11:30:38PM -0000, jakub@gcc.gnu.org wrote:
 > Synopsis: Incorrect struct offset for unaligned 64-bit fields in debug information
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: jakub
 > State-Changed-When: Tue Apr 30 16:30:37 2002
 > State-Changed-Why:
 >     You have not provided t64.cpp (or better t64.ii if t64.cpp
 >     includes some headers).
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6522
 
 I can confirm this in 3.1.  It's present in 3.0, but worked in 2.95.3. 
 It's quite annoying, since GDB can't infer the right answer.
 
 Here's another example:
 
 typedef __complex__ float cf;
 struct x { char c; cf f; } __attribute__ ((__packed__));
 struct unpacked_x { char c; cf f; };
 
 Compile and compare the debug info; it does not respect __packed__.
 
 -- 
 Daniel Jacobowitz                           Carnegie Mellon University
 MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2002-05-03  1:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 18:42 Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-03  3:56 Daniel Jacobowitz
2003-01-02 18:36 Nathanael Nerode
2002-05-03 10:36 Daniel Jacobowitz
2002-05-03  3:26 Jakub Jelinek
2002-05-01  6:16 Fred Young
2002-04-30 16:30 jakub
2002-04-30 13:56 fred

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020503013602.30131.qmail@sources.redhat.com \
    --to=drow@mvista.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).