public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8960: [3.2/3.3 regression] Segfault with __attribute__ ((mode (...))) in start_function:5702
Date: Sat, 21 Dec 2002 09:06:00 -0000 [thread overview]
Message-ID: <20021221170601.8529.qmail@sources.redhat.com> (raw)
The following reply was made to PR c/8960; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Christian Ehrhardt <ehrhardt@mathematik.uni-ulm.de>
Cc: bangerth@dealii.org, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
<nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c/8960: [3.2/3.3 regression] Segfault with __attribute__ ((mode
(...))) in start_function:5702
Date: Sat, 21 Dec 2002 10:59:15 -0600 (CST)
> Ooops. One shouldn't change test cases in the very last minute :-(
>
> __attribute__ ((mode (TI))) int f (void) { }
>
> (note TI instead of SI) indead crashes on 3.2/3.3 as described and
> issues an error with 2.95.3 on sparc:
>
> 7227-2.c:2: no data type for mode `TI'
>
> However, this testcase results in an error with all gcc Versions on i386.
Right. No crash on x86, but regression on sparc. And crash on x86 with all
versions and old testcase. Not better, anyway.
Danke
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-12-21 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 9:06 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-21 8:46 Christian Ehrhardt
2002-12-20 20:36 bangerth
2002-12-16 6:36 Christian Ehrhardt
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=20021221170601.8529.qmail@sources.redhat.com \
--to=bangerth@ticam.utexas.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).