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

2 msg	How to remove the option -Qy to as
1 msg	gcc-4.2-20070829 is now available
4 msg	Bug or feature? C++ code that no longer compile...
7 msg	Stage 2 project: upgrade decNumber
3 msg	sync_fetch_and_add creating unrecognizable insn
1 msg	Announce: MPFR 2.3.0 is released
2 msg	Re: r127885 - in /trunk: ChangeLog config.sub
9 msg	ICE in langhooks.c on SPU
14 msg	question about rtl loop-iv analysis
2 msg	Gcc error - configure: error: C compiler cannot...
5 msg	another build failure on ppc64-linux
1 msg	gcc-4.1-20070827 is now available
4 msg	use of ifndef inhibit_libc to disable the conte...
3 msg	Build failure on ppc64
1 msg	[tuples] Merged with mainline
2 msg	Issues with the constification patches

PING SC members [was RE: RFA: GCC 4.2.1: Stabal...
\ Dave Korn (27 Aug 2007)
. \ Mark Mitchell (28 Aug 2007)
. . \ Gerald Pfeifer (16 Sep 2007)
. . . \ Dave Korn (17 Sep 2007)
. \ Geoffrey Keating (29 Sep 2007)

3 msg	Bootstrap failure with --enable-checking=all,rtl
1 msg	[possible BUG] gcc's vcg creation code (-dv flag)
1 msg	va_ref

Subject:	Re: PING SC members [was RE: RFA: GCC 4.2.1: Stabalizing coalesce_list's qsort]
Group:	Gcc
From:	Mark Mitchell
Date:	28 Aug 2007

Dave Korn wrote:
> On 23 August 2007 22:34, Mark Mitchell 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.
>
> Hear, hear. I've always thought these principles were meant to be sacrosanct,
> but now I try to look it up, I don't see them explicitly listed in either the
> development methodology, the release criteria, or anywhere else likely-looking.

> Can the SC please consider adding these requirements explicitly to the list of
> "Design and Development Goals" in the mission statement? Or would it make more
> sense as part of the development methodology, or the portability section of the
> gcc-specific coding conventions?

I don't think this needs to be part of the mission statement; it's more
of a technical nitty-gritty than that. But, I think putting into the
coding conventions is a good idea.

Thanks,

--
Mark Mitchell
CodeSourcery
mark
(650) 331-3385 x713