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: help writing gcc code

From: "Wei Chen" <smartchenwei at gmail dot com>
To: "Brooks Moses" <brooks dot moses at codesourcery dot com>
Cc: "Mike Stump" <mrs at apple dot com>, AaronCloyd <acloy001 at gmail dot com>, gcc at gcc dot gnu dot org
Date: Tue, 22 May 2007 11:05:21 +0800
Subject: Re: help writing gcc code
References: <10727717.post@talk.nabble.com> <A41B5ADA-280B-41C7-A7CF-D31415CD8E4F@apple.com> <46525D1E.6030207@codesourcery.com>

i think you can read GCC backend to understand GCC how to
write .s files.

On 5/22/07, Brooks Moses <brooks.moses@codesourcery.com> wrote:

Mike Stump wrote:
> On May 21, 2007, at 2:43 PM, AaronCloyd wrote:
>> I need to edit a gcc source code, then recompile.
>
> Wrong list...  gcc-help is closer that what you want...

Is it?  Changing the internals of what GCC puts into .s files seems a
topic that's more appropriate here, I would think.

- Brooks

--
i'm a newbie in GCC community.
Wei Chen

References:
- help writing gcc code
  - From: AaronCloyd
- Re: help writing gcc code
  - From: Mike Stump
- Re: help writing gcc code
  - From: Brooks Moses

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