This is the mail archive of the gcc-patches@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: [PATCH] Add support for the Win32 hook prologue (try 2)

From: Stefan Dösinger <stefan at codeweavers dot com>
To: Paolo Bonzini <bonzini at gnu dot org>
Cc: gcc-patches at gcc dot gnu dot org
Date: Fri, 11 Sep 2009 00:51:28 +0200
Subject: Re: [PATCH] Add support for the Win32 hook prologue (try 2)
References: <200909091652.15133.stefan@codeweavers.com> <200909110042.21265.stefan@codeweavers.com> <4AA98140.7070109@gnu.org>

Am Friday 11 September 2009 00:44:16 schrieb Paolo Bonzini:
> On 09/11/2009 12:42 AM, Stefan Dösinger wrote:
> > Am Friday 11 September 2009 00:31:37 schrieb Paolo Bonzini:
> >>> What are the formatting imprecisions you talked about though?
> >>
> >> Spaces between function name and (, and possibly overlong lines.
> >
> > I added a space betwee function name and (, and between __attribute__ and
> > ( . When is a line considered an overlong line? The longest I have in
> > this test is 73 chars.
>
> I noticed the formatting imprecision in the i386.c part, actually.  80
> characters is fine.
Ok - fixed them in i386.c as well. Lets hope I got all of them

Follow-Ups:
- Add support for the Win32 hook prologue (try 3)
  - From: Stefan Dösinger

References:
- [PATCH] Add support for the Win32 hook prologue
  - From: Stefan Dösinger
- Re: [PATCH] Add support for the Win32 hook prologue (try 2)
  - From: Stefan Dösinger
- Re: [PATCH] Add support for the Win32 hook prologue (try 2)
  - From: Paolo Bonzini

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