public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de
To: adam@os.inf.tu-dresden.de, ehrhardt@mathematik.uni-ulm.de,
	gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/9373: [<3.3,3.4> regression] ICE with -fstrict-aliasing in set_mem_alias_set, at emit-rtl.c:1932
Date: Mon, 20 Jan 2003 15:47:00 -0000	[thread overview]
Message-ID: <20030120154745.25496.qmail@sources.redhat.com> (raw)

Old Synopsis: GCC-3.3 internal compiler error with -fstrict-aliasing
New Synopsis: [<3.3,3.4> regression] ICE with -fstrict-aliasing in set_mem_alias_set, at emit-rtl.c:1932

Responsible-Changed-From-To: cae->unassigned
Responsible-Changed-By: cae
Responsible-Changed-When: Mon Jan 20 15:47:44 2003
Responsible-Changed-Why:
    Testcase reduced.
State-Changed-From-To: open->analyzed
State-Changed-By: cae
State-Changed-When: Mon Jan 20 15:47:44 2003
State-Changed-Why:
    Here's a reduced test case that ICEs with 3.4 on sparc-sun-solaris
    and linux-gnu-i686: This reduced testcase is probably no longer legal
    but as I can't comment on the legality of the original code I leave this
    in ice-on-legal state. Priority high because this is a regression from 3.2.
    
    ------------- cut ---------------------------------
    typedef unsigned int Mword;
    struct Thread
    {
      Mword sys_ipc_log();
      void hook_ipc_vector();
      unsigned (Thread::*syscall_table)();
    };
    
    void Thread::hook_ipc_vector()
    {
        syscall_table = &Thread::sys_ipc_log;
    }
    ------------- cut ---------------------------------
    
    Compile with -fstrict-aliasing. Here's the ICE again:
    
    9373-2.cc: In member function `void Thread::hook_ipc_vector()':
    9373-2.cc:11: internal compiler error: in set_mem_alias_set, at emit-rtl.c:1934
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9373


                 reply	other threads:[~2003-01-20 15:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030120154745.25496.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --cc=adam@os.inf.tu-dresden.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).