public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "florent dot gallet at orange dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/17054] New: internal compiler error: in make_decl_rtl, at varasm.c:752 Date: Mon, 16 Aug 2004 23:17:00 -0000 [thread overview] Message-ID: <20040816231701.17054.florent.gallet@orange.fr> (raw) Well it's easy to make the prog work, but I still report it To reproduce : typedef struct tagS { long a; long b; long c; } S; int i; S g(const S &); S g(); int f() { return 0; } S g(const S &toto) { // the error is here int h = f(); S tata = {toto.a, toto.b, h}; return tata; } S g() { S toto; return g(toto); } -- Summary: internal compiler error: in make_decl_rtl, at varasm.c:752 Product: gcc Version: 3.4.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: florent dot gallet at orange dot fr CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17054
next reply other threads:[~2004-08-16 23:17 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-16 23:17 florent dot gallet at orange dot fr [this message] 2004-08-17 0:15 ` [Bug c++/17054] " pinskia 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=20040816231701.17054.florent.gallet@orange.fr \ --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: linkBe 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).