From: David Edelsohn <dje@watson.ibm.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: Kevin Buettner <kevinb@cygnus.com>,
"Zack Weinberg" <zackw@Stanford.EDU>,
Matthew Conway <matt_conway@i2.com>,
Mark Mitchell <mark@codesourcery.com>,
gcc-patches@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Limited success with 3.0 branch on AIX
Date: Thu, 17 May 2001 15:27:00 -0000 [thread overview]
Message-ID: <200105172226.SAA25498@makai.watson.ibm.com> (raw)
In-Reply-To: <15107.21410.608878.788866@kwikemart.cygnus.com>
>>>>> Elena Zannoni writes:
Elena> I would prefer to do option 3, so that it would work no matter what.
Elena> But if we all agree that we can take the risk of not having gcc2_compiled
Elena> defined at all, then we are off the hook.
Don't everyone answer at once!
Avoiding gcc2_compiled altogether would seem best to me. I defer
to the GDB developers whether this is correct.
I am a bit concerned about removing gcc2_compiled on AIX and not
making this a broader policy across all targets because some dependency
could slip in.
Instead of "gcc2_compiled", it seems better for GCC to utilize
whatever compiler version information or compiler-specific information is
allowed in the object format. Is N_OPT really the standard? Where do HP
and SGI and Intel and Greenhills and Metrowerks and other place their
version information?
David
next prev parent reply other threads:[~2001-05-17 15:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15106.54023.177141.275660@kwikemart.cygnus.com>
2001-05-16 12:37 ` David Edelsohn
2001-05-16 13:07 ` David Edelsohn
2001-05-16 13:51 ` Kevin Buettner
2001-05-16 14:06 ` Stan Shebs
2001-05-16 14:10 ` David Edelsohn
2001-05-16 14:32 ` Elena Zannoni
2001-05-16 21:29 ` Elena Zannoni
2001-05-17 15:27 ` David Edelsohn [this message]
[not found] <200104302116.RAA23290@makai.watson.ibm.com>
2001-05-02 23:25 ` Zack Weinberg
2001-05-03 1:42 ` Kevin Buettner
2001-05-15 15:27 ` Elena Zannoni
2001-05-15 15:31 ` David Edelsohn
2001-05-15 16:19 ` Elena Zannoni
2001-05-16 10:46 ` David Edelsohn
2001-05-16 11:15 ` David Edelsohn
2001-05-16 12:24 ` Elena Zannoni
[not found] <OF70310855.A41D4A39-ON86256A39.00616113@i2.com>
2001-05-01 10:13 ` David Edelsohn
2001-05-01 13:02 ` Daniel Berlin
2001-05-01 13:22 ` David Edelsohn
2001-05-01 15:40 ` Kevin Buettner
2001-05-01 15:44 ` David Edelsohn
2001-05-01 16:21 ` Kevin Buettner
2001-05-01 19:15 ` David Edelsohn
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=200105172226.SAA25498@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=ezannoni@cygnus.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kevinb@cygnus.com \
--cc=mark@codesourcery.com \
--cc=matt_conway@i2.com \
--cc=zackw@Stanford.EDU \
/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