This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Apple specific options: patch to include them in the current release gcc?

From: Dale Johannesen <dalej at apple dot com>
To: Matt Austern <austern at apple dot com>
Cc: gcc at gcc dot gnu dot org, Dale Johannesen <dalej at apple dot com>, Stan Shebs <shebs at apple dot com>, "Remy X.O. Martin" <vsxo at hotmail dot com>
Date: Thu, 27 Jan 2005 20:33:23 -0800
Subject: Re: Apple specific options: patch to include them in the current release gcc?
References: <20050127224756.4c605f7e@portia.local> <41F9AF13.4000908@apple.com> <BE7EC1E0-D74A-4613-99F6-6A5BB2B8D8CD@apple.com>

On Jan 27, 2005, at 8:22 PM, Matt Austern wrote:

- Patches that we haven't even bothered to submit because we're pretty sure they'd be rejected. (Example: alternate asm syntax that's more compatible with CodeWarrior and Visual C++.)

Actually, Stan submitted this and it was firmly rejected. A better example is some common-code optimizer tweaks that are not applicable or negative for other targets. These can sometimes be gotten into mainline by adding new macros, but people are skeptical of such changes, rightly so.

Follow-Ups:
- Re: Apple specific options: patch to include them in the currentrelease gcc?
  - From: Stan Shebs

References:
- Apple specific options: patch to include them in the currentrelease gcc?
  - From: Remy X.O. Martin
- Re: Apple specific options: patch to include them in the currentrelease gcc?
  - From: Stan Shebs
- Re: Apple specific options: patch to include them in the current release gcc?
  - From: Matt Austern

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]