public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "headch at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48446] New: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:1946
Date: Tue, 05 Apr 2011 03:54:00 -0000	[thread overview]
Message-ID: <bug-48446-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48446

           Summary: internal compiler error: in gimplify_var_or_parm_decl,
                    at gimplify.c:1946
           Product: gcc
           Version: 4.4.5
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: headch@gmail.com


Created attachment 23878
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23878
The failing source file

I compile the attached file using this command:

$ g++ -std=gnu++0x -Wall -Wextra -c test.cpp

with this version of GCC:

$ gcc --version
gcc (Gentoo 4.4.5 p1.2, pie-0.4.5) 4.4.5
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

on Gentoo x86-64 and x86 (both produce identical error messages). I get this
output:

test.cpp: In member function ‘void Sender::flush()’:
test.cpp:168: internal compiler error: in gimplify_var_or_parm_decl, at
gimplify.c:1946
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.gentoo.org/> for instructions.

I also have access to an OpenSUSE x86-64 environment reading out this version:

$ gcc --version
gcc (SUSE Linux) 4.5.0 20100604 [gcc-4_5-branch revision 160292]
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

This gives the following output:

test.cpp: In member function ‘void Sender::flush()’:
test.cpp:175:71: internal compiler error: in gimplify_var_or_parm_decl, at
gimplify.c:1816
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.opensuse.org/> for instructions.

(yes, the source line number of the error in test.cpp is different for this GCC
version even though the sources are identical).

Finally, a friend using Arch Linux x86-64 tested the same code on GCC 4.6 and
also reproduced the bug, though I don't have the line numbers from that test.

I can attach preprocessed source if you want, though the source doesn't use
anything but standard headers and the problem seems quite easily reproducible
as I already described.


             reply	other threads:[~2011-04-05  3:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05  3:54 headch at gmail dot com [this message]
2011-04-05 11:14 ` [Bug c++/48446] " rguenth at gcc dot gnu.org
2011-04-05 11:23 ` redi at gcc dot gnu.org
2011-04-05 11:30 ` [Bug c++/48446] [4.3/4.4/4.5/4.6 Regression] " redi at gcc dot gnu.org
2011-04-05 11:57 ` rguenth at gcc dot gnu.org
2011-04-07  8:31 ` jakub at gcc dot gnu.org
2011-04-07  8:36 ` jakub at gcc dot gnu.org
2011-04-07  8:55 ` jakub at gcc dot gnu.org
2011-04-10 10:47 ` rguenth at gcc dot gnu.org
2011-04-14 15:00 ` jason at gcc dot gnu.org
2011-04-14 15:22 ` jason at gcc dot gnu.org
2011-05-02 18:42 ` jason at gcc dot gnu.org
2011-05-06 22:03 ` jason at gcc dot gnu.org
2011-05-07  1:54 ` jason at gcc dot gnu.org

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=bug-48446-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).