Re: GCC 4.3.0 Status Report (2007-09-04)

Mark, > Kai Tietz wrote: > > >> Kai, why is your change making OUTGOING_REG_PARM_STACK_SPACE accept a > >> FUNCTION_DECL, rather than a FUNCTION_TYPE? I'd think that all > >> calling-convention predicates ought to be looking at the type to support > >> calling through function pointers? > > >

libstdc++-v3/include/precompiled weirdness

I've recently noticed that every time I build GCC, the source files in the libstdc++-v3/include/precompiled directory have their modification timestamps updated. Anyone know what's going on here? Ollie

Should -ftrapv check type conversion?

I've been looking at -ftrapv and some simple cases it doesn't work right in. (I've got a patch coming soon to address one case where __addvsi3 libcalls and the like get optimized away in RTL.) I see a few reports in Bugzilla, many marked as duplicates of PR 19020 though they cover a few di

Re: Trap floating-point exceptions?

On Sun, 2007-09-16 at 20:51 -0700, Ralf W. Grosse-Kunstleve wrote: > Under Linux, gcc/g++-compiled code happily continues running after > producing NAN and INF. Often it is time-consuming to backtrack to the > actual source of the numerical problems. In addition, such problems may > go undetected

Trap floating-point exceptions?

Under Linux, gcc/g++-compiled code happily continues running after producing NAN and INF. Often it is time-consuming to backtrack to the actual source of the numerical problems. In addition, such problems may go undetected for some time, which can cause all kinds of confusion. Other platforms sto

RE: PING SC members [was RE: RFA: GCC 4.2.1: Stabalizing coalesce_list's qsort]

On 17 September 2007 00:28, Gerald Pfeifer wrote: > On Tue, 28 Aug 2007, Mark Mitchell wrote: >> Dave Korn wrote: I do think that generating the same code, independent of host system, is a very important property of GCC's design, just like generating the same code independent of whe

RE: Coding conventions -- command line option vs command-line option

On 17 September 2007 00:35, Gerald Pfeifer wrote: > And now to the most important issue of all to address before we can > release GCC 4.3.0. ;-) > > In our current documentation we have both "command-line option" and > "command line option". Like other such cases, we should make a choice > and d

Coding conventions -- command line option vs command-line option

And now to the most important issue of all to address before we can release GCC 4.3.0. ;-) In our current documentation we have both "command-line option" and "command line option". Like other such cases, we should make a choice and document this in codingconventions.html. I am willing to take c

Re: PING SC members [was RE: RFA: GCC 4.2.1: Stabalizing coalesce_list's qsort]

On Tue, 28 Aug 2007, Mark Mitchell wrote: > Dave Korn wrote: >>> I do think that generating the same code, independent of host system, is >>> a very important property of GCC's design, just like generating the same >>> code independent of whether or not we're compiling with -g. >> Can the SC plea

Re: Question about rs6000 zero_fp_constant predicate

> I want to create a rtx which will fit the description of the following > operand. (taken from selv2sf4 instruction in the rs6000/paired.md machine > description) > > (match_operand:SF 4 "zero_fp_constant" "F") > > I am not sure how to create such zero const_double rtx and I appreciate > help rega

Question about rs6000 zero_fp_constant predicate

Hello, I want to create a rtx which will fit the description of the following operand. (taken from selv2sf4 instruction in the rs6000/paired.md machine description) (match_operand:SF 4 "zero_fp_constant" "F") I am not sure how to create such zero const_double rtx and I appreciate help regarding