From: Andrew Cagney <ac131313@cygnus.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Hmm, GCC are catching up :-)
Date: Tue, 21 Aug 2001 06:42:00 -0000 [thread overview]
Message-ID: <3B817D95.7060504@cygnus.com> (raw)
In-Reply-To: <200108201931.f7KJVkn18615@localhost.localdomain>
> In article < 3B7DF561.6070609@cygnus.com > you write:
>
>>See:
>>
>> http://gcc.gnu.org/ml/gcc/2001-08/msg00824.html
>>
>>GDB has been persuing this strategy for some time.
>
>
> Won't this potentially cause undefined references at -O0? Or is
> the point that GCC prunes dead code even at -O0?
It is that GCC (and the GNU coding standard) are moving away from #ifdef
spagetti.code - a brave but necessary decision.
This is something GDB, due to multi-arch, has been persuing for some time.
enjoy,
Andrew
prev parent reply other threads:[~2001-08-21 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 21:56 Andrew Cagney
2001-08-20 12:31 ` Jonathan Larmour
2001-08-21 6:42 ` Andrew Cagney [this message]
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=3B817D95.7060504@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=jlarmour@redhat.com \
/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