public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chip Salzenberg <chip@rio.atlantic.net>
To: egcs@cygnus.com
Subject: 970929: MY patch list
Date: Wed, 08 Oct 1997 06:04:00 -0000	[thread overview]
Message-ID: <199710081303.JAA06737@rio.atlantic.net> (raw)

(I mailed this once, but haven't seen it; apologies if it's a dup for you.)

H.J. still can't duplicate my exception problem.  I've applied the
following patches; is any of them a Bad Idea when debugging exceptions?

#00:
    Thu Oct  2 14:28:30 1997  David S. Miller  <davem@tanya.rutgers.edu>
	* explow.c (optimize_save_area_alloca): New function for targets
	where SETJMP_VIA_SAVE_AREA is true.
	(allocate_dynamic_stack_space): On SETJMP_VIA_SAVE_AREA targets,
	compute the amount of stack space needed should we find later that
	setjmp is never called by this function, stuff rtl for this inside
	a REG_NOTE of the final SET of stack_pointer_rtx.
	* toplev.c (rest_of_compilation): If SETJMP_VIA_SAVE_AREA and
	current_function_calls_alloca, call optimize_save_area_alloca.

#01:
    n/a

#02:
    Tue Sep 30 11:05:47 1997  Richard Henderson  <rth@cygnus.com>
	* i386.h (RETURN_ADDR_RTX): New definition that works for 
	__builtin_return_address(0) and -fomit-frame-pointer.

#03:
    Wed Oct  1 15:37:58 CEST 1997  Thomas Koenig (ig25@rz.uni-karlsruhe.de)
	* cp/parse.y: Remove duplicate definition of PFUNCNAME

#04:
    Wed Oct  1 23:51:06 CEST 1997  Thomas Koenig (ig25@rz.uni-karlsruhe.de)
	* reload.c (decompose): Always initialize val.base.

#05:
    Wed Oct  1 17:47:48 1997  Richard Henderson  <rth@cygnus.com>
	* expr.c (get_inner_reference): Remove the array bias after 
	converting the index to Pmode.

#06:
    Tue Sep 30 08:51:36 1997  Jason Merrill  <jason@yorick.cygnus.com>
        * method.c (build_decl_overload_real): Reformat.

#07:
    1997-10-04  Andreas Schwab  <schwab@issan.informatik.uni-dortmund.de>
	* frame.c (__frame_state_for): Execute the FDE insns until the
	current pc value is strictly bigger than the target pc value.

#08:
    Tue Sep 30 16:50:55 CEST 1997  Thomas Koenig  (ig25@rz.uni-karlsruhe.de)
	* cccp.c: (struct file_buf) change system_header_p to int
          (expand_to_temp_buffer) initialize all members of obuf

#09:
    Fri Oct  3 10:42:37 1997  Mark Mitchell  <mmitchell@usa.net>
	* decl.c (make_typename_type): Do not try to call lookup_field for
	non-aggregate types.

#10:
    Fri Oct  3 11:56:36 1997  Jason Merrill  <jason@yorick.cygnus.com>
	* toplev.c (rest_of_compilation): Defer all non-nested inlines.

#11:
    Alexandre Oliva <oliva@dcc.unicamp.br>
	* libio.h: _G_HAVE_PRINTF_FP's value must be tested, not its
	definition
	* iostream.cc: ditto

#12:
    "... patch by Jeff Law that fixes the suboptimal recognition of
     GIVs due to removal of some special case ARRAY_REF code from
     expand_expr (see [Toon Moene's] mail dd 14th of September)"
	* loop.c

-- 
Chip Salzenberg          - a.k.a. -           <chip@pobox.com>
        "He's Mr. Big of 'Big And Tall' fame."  // MST3K

             reply	other threads:[~1997-10-08  6:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-08  6:04 Chip Salzenberg [this message]
1997-10-08 14:41 ` H.J. Lu
1997-10-08 21:19   ` chip
1997-10-09  9:26     ` Michael Alan Dorman
1997-10-10 15:09     ` H.J. Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199710081303.JAA06737@rio.atlantic.net \
    --to=chip@rio.atlantic.net \
    --cc=egcs@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).