public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com
To: gcc-gnats@gcc.gnu.org
Cc: ghazi@caip.rutgers.edu, kenner@vlsi1.ultra.nyu.edu
Subject: c++/6212: g++ testsuite EH regressions for irix6 -mabi=64
Date: Sat, 06 Apr 2002 22:56:00 -0000	[thread overview]
Message-ID: <20020407064945.21167.qmail@sources.redhat.com> (raw)


>Number:         6212
>Category:       c++
>Synopsis:       g++ testsuite EH regressions for irix6 -mabi=64
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 06 22:56:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     David Billinghurst
>Release:        3.1 and 3.2
>Organization:
>Environment:
mips-sgi-irix6.5
mips-sgi-irix6.2
>Description:
There are around 100 failures in g++ testsuite with 3.1 on 
irix 6.5.  They are runtime failures consistent with broken 
exception handling.

Looking back through gcc-testresults
 - 20010529 is OK (http://gcc.gnu.org/ml/gcc-testresults/2001-05/msg00714.html)
 - 20010611 fails (http://gcc.gnu.org/ml/gcc-testresults/2001-06/msg00276.html)


There was some discussion at the time:
 - http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg00894.html
 - http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg01005.html
 - http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg01489.html

which pointed to patch:

Sat Jun  2 06:53:50 2001  Richard Kenner  <kenner@vlsi1.ultra.nyu.edu>

	* tree.h (struct record_layout_info_s): New field unpadded_align.
	(set_lang_adjust_rli): New declaration.
	* stor-layout.c (layout_decl): If DECL is packed, but at alignment
	it would have if not packed, do not downgrade DECL_ALIGN.
	(lang_adjust_rli, set_lang_adjust_rli): New.
	(start_record_layout): Initialize new field unpadded_align.
	(debug_rli): Display it.
	(place_union_field, place_field): Set it.
	(layout_type, case RECORD_TYPE): Call via lang_adjust_rli if set.

	* print-tree.c (print_node): Don't print "regdecl" when bit doesn't
	mean that; use proper names instead.
	Print DECL_NO_STATIC_CHAIN.

	* except.c (expand_builtin_frob_return_addr): Add missing call
	to convert_memory_address #ifdef POINTERS_EXTEND_UNSIGNED.
	(expand_builtin_eh_return): Likewise.
	(expand_eh_return): Clean up ptr_mode != Pmode cases.

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-07  6:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06 22:56 David.Billinghurst [this message]
2002-04-16 18:07 rth
2002-04-16 19:06 rth
2002-04-16 19:26 Billinghurst, David (CRTS)
2002-04-17 17:16 Billinghurst, David (CRTS)
2002-04-17 17:56 Kaveh R. Ghazi
2002-04-21 20:46 Billinghurst, David (CRTS)
2002-04-21 21:06 Billinghurst, David (CRTS)
2002-04-22  3:46 Richard Kenner
2002-04-22 19:26 Billinghurst, David (CRTS)
2002-04-23  0:38 rth
2002-04-24 11:14 rth
2002-04-30 20:36 Billinghurst, David (CRTS)
2002-04-30 21:36 Richard Henderson
2002-04-30 21:56 Kaveh R. Ghazi
2002-04-30 23:26 Richard Henderson
2002-05-06 22:46 rth

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=20020407064945.21167.qmail@sources.redhat.com \
    --to=david.billinghurst@riotinto.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).