Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] wrong pointer type length
Date: Thu, 17 May 2007 17:01:00 -0000	[thread overview]
Message-ID: <m3irar8jwj.fsf@codesourcery.com> (raw)
In-Reply-To: <20070517161919.GA508@adacore.com> (Joel Brobecker's message of "Thu, 17 May 2007 09:19:19 -0700")


Joel Brobecker <brobecker@adacore.com> writes:
> We traced down the problem to the fact that the native assembler
> seems to be changing up the order in which the stabs entries are
> generated. Not sure why. Perhaps Ulrich might know a bit more.
> In any case, the assembly file contains the following stabx entries
> in that order:
>
>         .stabx "root__union_record_t:Tt42=s12x_part:40,0,32;[...]
>         .stabx  "root__union_record_a:t43=*42",0,140,0
>         .stabx  "u:p74=k43",808,130,0
>
> However, after being compiled, the order has been changed to:
>
>         1. root__union_record_t:Tt42=s12x_part:40,0,32;[...]
>         2. u:p74=k43
>         3. root__union_record_a:t43=*42

If the assembler is doing this in other cases, you're going to be
pretty hosed.  STABS requires records to appear in the order
specified.


  parent reply	other threads:[~2007-05-17 17:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 16:19 Joel Brobecker
2007-05-17 16:27 ` Daniel Jacobowitz
2007-05-17 16:42   ` Joel Brobecker
2007-05-17 18:51     ` [RFA] wrong pointer type length part 2 (of 2) Joel Brobecker
2007-05-17 20:07       ` Daniel Jacobowitz
2007-05-17 20:16         ` Joel Brobecker
2007-05-17 17:01 ` Jim Blandy [this message]
2007-05-17 17:23   ` [RFA] wrong pointer type length Joel Brobecker

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=m3irar8jwj.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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