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: __builtin_va_list bug or feature

From: Richard Henderson <rth at redhat dot com>
To: Gisle Vanem <gvanem at eunet dot no>
Cc: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>, gcc at gcc dot gnu dot org
Date: Fri, 25 Apr 2003 14:20:11 -0700
Subject: Re: __builtin_va_list bug or feature
References: <1a0201c30b35$525af210$0600000a@broadpark.no> <Pine.LNX.4.53.0304251758130.25878@kern.srcf.societies.cam.ac.uk> <004101c30b54$c7401550$0600000a@broadpark.no>

On Fri, Apr 25, 2003 at 08:02:04PM +0200, Gisle Vanem wrote:
> I'd rather prefer wrong output than a generated trap. Which neither
> MingW nor djgpp have handlers for.  Seems gcc is biased towards Linux
> in this case.

I'm surprised there's no handler installed to generate 
some sort of signal in this case -- seems like a point
that could be improved for mingw and djgpp.

Anyway, if you'd rather we call abort instead, you can
comment out the following pattern in gcc/config/i386/i386.md:

	(define_insn "trap"
	  [(trap_if (const_int 1) (const_int 5))]
	  ""
	  "int\t$5")

r~

References:
- __builtin_va_list bug ir feature
  - From: Gisle Vanem
- Re: __builtin_va_list bug ir feature
  - From: Joseph S. Myers
- Re: __builtin_va_list bug or feature
  - From: Gisle Vanem

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