public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* making a 2.95.4 release
@ 2002-03-28  9:35 David O'Brien
  2002-03-28  9:39 ` law
                   ` (3 more replies)
  0 siblings, 4 replies; 18+ messages in thread
From: David O'Brien @ 2002-03-28  9:35 UTC (permalink / raw)
  To: Jeff Law; +Cc: gcc

Hello Jeff,

As GCC 2.95 release engineer, would you please create a 2.95.4 release
from the 'gcc-2_95-branch'?  Considering the maturity of the branch, I
cannot imagine this would take much more than creating the tarballs and
putting them on ftp.gnu.org.

The BSD's need 2.95.4 because critical setjump/longjump exception
handling bugs are finally fixed.  Debian uses 2.95 for other reasons.
EGCS 1.0.3 was created for the needs of Red Hat and GCC 2.95.3 for the
needs of glibc (Message-Id: <200203230150.RAA10697@atrus.synopsys.com>).
So I there is precedence for making a release for the needs of a class of
other, non-GCC, software.

For various reason people are still downloading and using 2.95.3 to this
day.  GCC 3.x is also inappropriate for some of the BSD releases due to
the major changes between 2.95->3.0.  Just this week someone else was
asking for a 2.95.4 release.

Below are the changes since 2.95.3.

-- 
-- David  (obrien@FreeBSD.org)


Index: ChangeLog
===================================================================
RCS file: /cvs/gcc/egcs/gcc/ChangeLog,v
retrieving revision 1.3667.4.336
retrieving revision 1.3667.4.363
diff -u -r1.3667.4.336 -r1.3667.4.363
--- ChangeLog	2001/03/16 12:52:02	1.3667.4.336
+++ ChangeLog	2001/10/03 00:45:49	1.3667.4.363
@@ -1,3 +1,169 @@
+2001-10-02  Zack Weinberg  <zack@codesourcery.com>
+
+	* gcc.c (main): Set this_file_error if the appropriate
+	compiler for a language has not been installed.
+
+2001-09-17  Philip Blundell  <philb@gnu.org>
+
+	* cccp.c (print_help): Fix typos.
+
+2001-08-29  David O'Brien  <obrien@FreeBSD.org>
+
+	* config/alpha/crtbegin.asm: The normal calling convention for alpha is
+	to re-initialize gp using 'ldgp gp,0(ra)' after a jsr instruction.
+
+2001-06-19  Bernd Schmidt  <bernds@redhat.com>
+
+	* regmove.c (optimize_reg_copy_3): Do nothing if previous insn
+	carries a REG_EQUIV note.  If it carries REG_EQUAL, delete the
+	note.
+
+2001-05-22  Bernd Schmidt  <bernds@redhat.com>
+
+	* sparc.md (movsf, movdf): Allow constant to integer reg moves.
+	(movsf, movdf splitters): Always split if there's an alignment
+	problem.
+
+2001-05-22  David Edelsohn  <dje@watson.ibm.com>
+
+	* rs6000.md (movsfcc,movdfcc): Remove NE case.
+
+2001-05-17  Bernd Schmidt  <bernds@redhat.com>
+
+	* function.c: Small formatting change to prevent compilation errors
+	on broken hpux systems.
+
+	* expr.c (protect_from_queue): Protect against subsequent calls to
+	emit_queue.
+	(expand_expr, case ADDR_EXPR): Prevent protect_from_queue from being
+	too clever.
+
+2001-04-06  Bernd Schmidt  <bernds@redhat.com>
+
+	2000-10-17  Franz Sirl  <Franz.Sirl-kernel@lauterbach.com>
+	* function.c (locate_and_pad_parm): Don't align stack unconditionally.
+
+	Thu Oct 28 10:20:02 1999  Geoffrey Keating  <geoffk@cygnus.com>
+	* config/rs6000/rs6000.md (movsf): Don't convert a SUBREG
+	of the function return register into a plain REG until
+	after function inlining is done.
+
+2001-04-04  Bernd Schmidt  <bernds@redhat.com>
+
+	Fri Nov  5 10:07:25 1999  Nick Clifton  <nickc@cygnus.com>
+	* function.c (is_addressof): New function.  Returns true if
+	the given piece of RTL is an ADDRESSOF.
+	(purge_addressof_1): Make boolean.  Return false if the
+	ADDRESSOFs could not be purged.
+	(purge_addressof): If ADDRESSOFs could not be purged from the
+	notes attached to an insn, remove the offending note(s),
+	unless they are attached to a libcall.
+
+2001-04-03  Bernd Schmidt  <bernds@redhat.com>
+
+	2001-03-16  Jakub Jelinek  <jakub@redhat.com>
+	* crtstuff.c (init_dummy): Use CRT_END_INIT_DUMMY if defined.
+	Remove ia32 linux PIC kludge and move it...
+	* config/i386/linux.h (CRT_END_INIT_DUMMY): ...here.
+
+	* loop.c (combine_movables): Restrict combinations of constants with
+	different modes so that we don't introduce SUBREGs into memory
+	addresses.
+
+	2001-02-02  Philip Blundell  <philb@gnu.org>
+	* arm/linux-elf.h (MAKE_DECL_ONE_ONLY, UNIQUE_SECTION_P): Define.
+	(UNIQUE_SECTION): Define.                                  
+
+	Wed Aug 25 15:27:22 1999  Gavin Romig-Koch  <gavin@cygnus.com>
+	* combine.c (nonzero_bits) : Allow single-ly set registers to be
+	anywere in the function only if they are pseudos and set before
+	being used (not live at the start of the function).
+	(num_sign_bit_copies) : Same.
+	(get_last_value_validate) : Same.
+	(get_last_value) : Same.
+
+	Fri Mar  3 12:49:28 2000  J"orn Rennecke <amylaar@cygnus.co.uk>
+        * reload1.c (reload_combine_note_use): Handle return register USEs.
+	REG case: Handle multi-hard-register hard regs.
+
+2001-03-30  Bernd Schmidt  <bernds@redhat.com>
+
+	* jump.c (delete_barrier_successors): Fix error in last change.
+
+	* reload1.c (delete_output_reload): Call eliminate_regs on substed.
+	(reload_as_needed): Call update_eliminable_offsets a bit later.
+
+	* final.c (cleanup_subreg_operands): Also clean up inside MEMs.
+
+	Mon Oct  4 02:31:20 1999  Mark Mitchell  <mark@codesourcery.com>
+	* mips.md: Define conditional move patterns for floating point
+	operands and DI mode conditions.
+
+	2000-11-25  Jakub Jelinek  <jakub@redhat.com>
+	* config/sparc/sparc.md (muldi3_v8plus): Remove H constraint.
+	Handle CONST_INT as second argument.
+
+2001-03-28  Bernd Schmidt  <bernds@redhat.com>
+
+	* flow.c (propagate_block): When trying to delete a case vector, cope
+	if its label has LABEL_PRESERVE_P set.
+	* jump.c (jump_optimize_1): Move call to delete_barrier_successors to
+	a point where JUMP_LABELS and LABEL_NUSES are set up properly.
+	(delete_barrier_successors): If deleting a table jump, delete the case
+	vector as well.
+	* varasm.c (force_const_mem): If we have a label, set LABEL_PRESERVE_P
+	so it won't get deleted.
+
+Tue Mar 20 18:31:48 2001  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
+
+	1999-11-30  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
+        * c-lex.c (yylex): With -Wtraditional, when the ANSI type of an
+	integer constant does not match the traditional type, limit the
+	warnings to cases where the base of the type is ten.
+
+        * invoke.texi (-Wtraditional): Document it.
+
+2001-03-20  David O'Brien  <obrien@FreeBSD.org>
+
+	from 2000-07-12  Zack Weinberg  <zack@wolery.cumb.org>
+	* final.c (profile_function): Do not emit profile counters in
+	the data section, if NO_PROFILE_COUNTERS is defined.
+	* tm.texi: Document NO_PROFILE_COUNTERS.  Update doc for
+	FUNCTION_PROFILER.
+
+	from 2000-10-02  David O'Brien  <obrien@dragon.nuxi.com>
+	* config/i386/freebsd.h (NO_PROFILE_COUNTERS): Define.
+
+2001-03-19  Bernd Schmidt  <bernds@redhat.com>
+
+	* version.c: Bump.
+
+	2000-01-18  Martin v. Löwis  <loewis@informatik.hu-berlin.de>
+	* c-parse.in (SAVE_WARN_FLAGS): Create an INTEGER_CST.
+	(RESTORE_WARN_FLAGS): Unpack it.
+	Change semantic type of extension to ttype.
+	* c-common.c (split_specs_attrs): Expect an INTEGER_CST.
+	* c-parse.y, c-parse.c, objc/objc-parse.y,
+	objc/objc-parse.c: Regenerate.
+
+	Wed Sep  1 09:12:02 1999  Jim Kingdon  <http://developer.redhat.com>
+	* c-parse.in: save and restore warn_pointer_arith on __extension__
+	along with pedantic.
+	(SAVE_WARN_FLAGS, RESTORE_WARN_FLAGS): Added.
+	Set the type of extension to itype rather than $<itype>1 kludge.
+	* extend.texi (Alternate Keywords): Adjust documentation.
+
+	Bring back the sjlj eh fixes.
+	* expr.c (expand_builtin_setjmp_setup): New.
+	(expand_builtin_setjmp_receiver): New.
+	(expand_builtin_setjmp): Split out _setup and _receiver functions.
+	Move argument parsing in from ...
+	(expand_builtin): ... here.
+	* except.c (receive_exception_label): Branch around receiver
+	unless new-style exceptions.  Call expand_builtin_setjmp_receiver.
+	(start_dynamic_handler): Call expand_builtin_setjmp_setup.
+	* expr.h: Update builtin setjmp decls.
+
 Fri Mar 16 12:46:19 GMT 2001 Bernd Schmidt  (bernds@redhat.com)
 
 	* gcc-2.95.3 Released.

^ permalink raw reply	[flat|nested] 18+ messages in thread
* Re: making a 2.95.4 release
@ 2002-03-31 12:14 Erik Schnetter
  0 siblings, 0 replies; 18+ messages in thread
From: Erik Schnetter @ 2002-03-31 12:14 UTC (permalink / raw)
  To: gcc

On Sun, 31 Mar 2002 14:06:18 +0200, Richard Zidlicky wrote:

> On Thu, Mar 28, 2002 at 09:22:14AM -0800, David O'Brien wrote:
>
> > For various reason people are still downloading and using 2.95.3 to this
> > day.  GCC 3.x is also inappropriate for some of the BSD releases due to
> > the major changes between 2.95->3.0.  Just this week someone else was
> > asking for a 2.95.4 release.
>
> yes, there are difference between 2.95 and 3.0 or 3.1. However for 
> many architectures 2.95 is too old and only additional headache.
> I would really appreciate if some of the bigger distributions would
> finally drop the old c**p. The fact that a few packages need little 
> patches is imho not an excuse to use a broken compiler forever.

gcc 3.0 was for a long time unsuitable for me due to bugs in preprocessing 
Fortran code.  gcc 3.0.4 is (finally) the first version that works for me.  I 
decided to switch not yet, because the C++ incompatibilities between 2.95 and 
3.0 would force me to recompile many libraries, and force me to compile some 
libraries myself where I can right now use a precompiled package.

I am using SuSE 7.3, and I am glad they did not swich to 3.0 that quickly.  
For me, the compilers are not the tools I develop, but are the tools I 
develop /with/.  Just knowing about the old bugs is often good enough for me, 
and is better than to spend a week or two recompiling everything, and finding 
new workarounds for the new bugs.

I am not asking for a 2.95.4 release, because 2.95.3 works fine for me.  But 
you should not call these versions "old c**p", because -- from my point of 
view -- the 3.0 releases are more broken than 2.95, in the very personal 
sense that I have had more problems with them so far.  3.0.4 seems to be all 
right by now, but I would still trust it less than 2.95.3.  I hope that the 
new SuSE 8.0 will be based on 3.0.4, but I even more hope it won't be based 
on 3.0.3.

-erik

-- 
Erik Schnetter <schnetter@uni-tuebingen.de>
Web: http://www.tat.physik.uni-tuebingen.de/~schnette/

^ permalink raw reply	[flat|nested] 18+ messages in thread
end of thread, other threads:[~2002-04-03 10:38 UTC | newest]

Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-03-28  9:35 making a 2.95.4 release David O'Brien
2002-03-28  9:39 ` law
2002-03-28  9:58 ` Gerald Pfeifer
2002-04-02  1:09   ` Gerald Pfeifer
2002-04-02 10:51     ` Joe Buck
2002-03-28 10:19 ` Bernd Schmidt
2002-03-28 11:38   ` David O'Brien
2002-03-28 11:46     ` Philip Blundell
2002-03-28 12:10       ` David O'Brien
2002-03-28 12:22         ` Daniel Jacobowitz
2002-03-28 11:57     ` Daniel Jacobowitz
2002-03-28 11:58     ` Bernd Schmidt
2002-03-28 12:14       ` David O'Brien
2002-03-28 12:29         ` Bernd Schmidt
2002-03-28 13:26         ` law
2002-04-03  2:57   ` Wolfram Gloger
2002-03-31  6:48 ` Richard Zidlicky
2002-03-31 12:14 Erik Schnetter

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).