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: Fri, 03 Jan 2003 03:56:00 -0000	[thread overview]
Message-ID: <20030103035601.12354.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: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	nobody@gcc.gnu.org, fred@nextnewgig.com
Subject: Re: target/6522: Incorrect struct offset for unaligned 64-bit fields in debug information
Date: Thu, 2 Jan 2003 22:51:48 -0500

 Hmm, I missed the patch going by, and the transition to feedback was
 before the testcase was provided.  The problem still exists in HEAD as
 of a day or two ago, so this is not fixed.
 
 [Huh.  I didn't realize a 64-bit integer could be misaligned when
 placed within a struct that didn't specify packedness.  This is a
 property of x86_field_align, in case anyone else gets confused looking
 at this testcase.  I've learned my one thing for today.]
 
 On Thu, Jan 02, 2003 at 01:34:20PM -0500, Nathanael Nerode wrote:
 > There was a patch to address this a while back.  Can someone confirm that 
 > this is fixed in mainline so we can close the bug (now in feedback for >6 
 > months)?
 > 
 > --Nathanael
 > 
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2003-01-03  3:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03  3:56 Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-02 18:36 Nathanael Nerode
2002-05-03 10:36 Daniel Jacobowitz
2002-05-03  3:26 Jakub Jelinek
2002-05-02 18:42 Daniel Jacobowitz
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=20030103035601.12354.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).