public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "smelkov at mph1 dot phys dot spbu dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/15461] New: [3.4 regression] ICE on valid code
Date: Sun, 16 May 2004 13:09:00 -0000	[thread overview]
Message-ID: <20040515131617.15461.smelkov@mph1.phys.spbu.ru> (raw)

---time.cpp--- 
struct A { 
    long tv_sec; 
}; 
 
class B { 
public: 
    operator A () const; 
}; 
 
inline B::operator A () const 
{ 
    int sec = 1; 
 
    A tv = { 
        tv_sec:  sec, 
    }; 
 
    return tv; 
} 
 
 
void xxx(const B& t) 
{ 
    A tv(t); 
} 
---end of time.cpp--- 
 
with gcc-3.3.3 it is ok. 
can't see whether this is related to PR14203 or not. 
 
[kirr@tugrik bug]$ g++340-check -O -Wall  -I include -c time.cpp -o time.o 
time.cpp: In function `void xxx(const B&)': 
time.cpp:11: internal compiler error: in make_decl_rtl, at varasm.c:752 
Please submit a full bug report, 
with preprocessed source if appropriate. 
See <URL:http://gcc.gnu.org/bugs.html> for instructions. 
 
[kirr@tugrik bug]$ g++340-check -v 
Reading specs from 
/usr/local/gcc-3.4.0-check/lib/gcc/i686-pc-linux-gnu/3.4.0/specs 
Configured with: ../gcc-3.4.0/configure --prefix=/usr/local/gcc-3.4.0-check 
--with-gnu-as --with-gnu-ld --enable-threads=posix --with-arch=i686 
--with-tune=pentium4 --enable-__cxa_atexit --enable-languages=c,c++,f77 
--enable-checking --disable-nls 
Thread model: posix 
gcc version 3.4.0

-- 
           Summary: [3.4 regression] ICE on valid code
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: smelkov at mph1 dot phys dot spbu dot ru
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2004-05-15 13:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 13:09 smelkov at mph1 dot phys dot spbu dot ru [this message]
2004-05-16 18:09 ` [Bug middle-end/15461] " pinskia at gcc dot gnu dot org
2004-06-19  6:10 ` ebotcazou at gcc dot gnu dot org
2004-06-20 11:47 ` [Bug c++/15461] " ebotcazou at gcc dot gnu dot org
2004-06-22  8:03 ` mmitchel at gcc dot gnu dot org
2004-06-22 13:55 ` bangerth at dealii dot org
2004-06-25 21:33 ` mmitchel at gcc dot gnu dot org
2004-07-02 16:44 ` mmitchel at gcc dot gnu dot org
2004-07-08 11:32 ` ebotcazou at gcc dot gnu dot org
2004-08-10  1:40 ` pinskia at gcc dot gnu dot org
2004-08-10 21:36 ` [Bug c++/15461] [3.4 regression] ICE due to NRV and inlining pinskia at gcc dot gnu dot org
2004-08-17  0:15 ` pinskia at gcc dot gnu dot org
2004-08-17 21:10 ` mmitchel at gcc dot gnu dot org
2004-08-25  5:33 ` cvs-commit at gcc dot gnu dot org
2004-08-25  5:52 ` pinskia at gcc dot gnu dot org
2004-08-25 15:16 ` cvs-commit at gcc dot gnu dot org
2004-09-13  8:39 ` cvs-commit at gcc dot gnu dot 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=20040515131617.15461.smelkov@mph1.phys.spbu.ru \
    --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).