public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmitry.petroff at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/62282] Undefined reference with __inline __attribute(__gnu_inline__) with -O0
Date: Thu, 28 Aug 2014 10:52:00 -0000	[thread overview]
Message-ID: <bug-62282-4-0keHV1ddYE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62282-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62282

--- Comment #3 from Dmitry Petrov <dmitry.petroff at gmail dot com> ---
Created attachment 33408
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33408&action=edit
g++ + gperf bug in action

Guys, I'm software developer myself and I can understand your attitute to
"declare bug as a feature". But please note, that this bug is breaking normal
development with gperf which is also a GNU tool.

In the attached archive try
make => failure in compiling bug++
make CFLAGS=-O => success, inlining happens
make CXX=clang++ => success

You're saying "we've designed this extension and it works as it should". But
why gcc links this successfully, but g++ don't? It looks like either C or C++
compiler bug.

P. S. I'm using gperf to generate code for both C server-side and C++
tools/testcases and such g++ behaviour is really unpleasing when making debug
builds.


  parent reply	other threads:[~2014-08-28 10:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 11:38 [Bug c++/62282] New: " dmitry.petroff at gmail dot com
2014-08-27 11:54 ` [Bug c++/62282] " rguenth at gcc dot gnu.org
2014-08-27 16:28 ` pinskia at gcc dot gnu.org
2014-08-28 10:52 ` dmitry.petroff at gmail dot com [this message]
2014-08-28 12:26 ` [Bug c++/62282] [4.8/4.9/5 Regression] " rguenth at gcc dot gnu.org
2014-08-28 12:27 ` rguenth at gcc dot gnu.org
2014-09-01  9:18 ` jakub at gcc dot gnu.org
2014-09-01 12:10 ` jakub at gcc dot gnu.org
2014-09-01 12:20 ` jakub at gcc dot gnu.org
2014-09-02 10:34 ` dmitry.petroff at gmail dot com
2014-09-02 10:47 ` jakub at gcc dot gnu.org
2014-09-02 11:48 ` dmitry.petroff at gmail dot com

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-62282-4-0keHV1ddYE@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).