public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13768] [3.4/3.5 Regression] -funit-at-a-time compiles unused inline function
Date: Tue, 03 Feb 2004 17:22:00 -0000 [thread overview]
Message-ID: <20040203172253.3226.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040120110040.13768.igodard@pacbell.net>
------- Additional Comments From mark at codesourcery dot com 2004-02-03 17:22 -------
Subject: Re: [3.4/3.5 Regression] -funit-at-a-time compiles
unused inline function
>Actually looking deeper into this specific testcase, I believe that if
>the source program was correct, unit-at-a-time would emit empty file
>too, since there is no entry point from where the call in question can
>be reached, so it just builds the program representation in memory prior
>optimizing it.
>This is because of your request to change C++ frontend that way (my
>initial patch didn't force instantiation of all TREE_USED templates).
>
>I think this is correct thing - GCC should error out on this testcase.
>Why it is considered a bug at first place?
>
>
If the vtable will not actually be emitted to the object file, then this
is not a bug, and you can close it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13768
next prev parent reply other threads:[~2004-02-03 17:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 11:00 [Bug c++/13768] New: syntax error only when -O2 igodard at pacbell dot net
2004-01-20 11:01 ` [Bug c++/13768] " igodard at pacbell dot net
2004-01-20 11:02 ` igodard at pacbell dot net
2004-01-20 11:03 ` igodard at pacbell dot net
2004-01-20 11:05 ` igodard at pacbell dot net
2004-01-20 15:49 ` [Bug c++/13768] [3.4/3.5 Regression] syntax error only when -funit-at-a-time pinskia at gcc dot gnu dot org
2004-01-20 17:18 ` [Bug optimization/13768] [3.4/3.5 Regression] -funit-at-a-time compiles unused inline function bangerth at dealii dot org
2004-01-21 3:26 ` pinskia at gcc dot gnu dot org
2004-01-21 5:22 ` igodard at pacbell dot net
2004-01-21 7:44 ` pinskia at gcc dot gnu dot org
2004-01-21 13:37 ` bangerth at dealii dot org
2004-01-31 18:22 ` pinskia at gcc dot gnu dot org
2004-02-03 8:39 ` [Bug c++/13768] " ebotcazou at gcc dot gnu dot org
2004-02-03 9:25 ` mmitchel at gcc dot gnu dot org
2004-02-03 11:00 ` hubicka at ucw dot cz
2004-02-03 15:46 ` mark at codesourcery dot com
2004-02-03 15:53 ` jh at suse dot cz
2004-02-03 15:59 ` jh at suse dot cz
2004-02-03 16:02 ` mmitchel at gcc dot gnu dot org
2004-02-03 16:04 ` hubicka at ucw dot cz
2004-02-03 17:22 ` mark at codesourcery dot com [this message]
2004-02-05 17:14 ` [Bug c++/13768] C++ fails to diagnose invalid code pinskia at gcc dot gnu dot org
2004-02-05 17:23 ` [Bug c++/13768] C++ fails to diagnose invalid code(calling a non exitsing function in a template class) in non unit-at-a-time mode giovannibajo at libero dot it
2004-02-05 20:04 ` [Bug c++/13768] Incoherent behaviour in instantiation between -funit-at-a-time and -fno-unit-at-a-time igodard at pacbell dot net
2004-05-05 20:25 ` hubicka at gcc dot gnu dot org
2004-08-03 6:03 ` 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=20040203172253.3226.qmail@sources.redhat.com \
--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).