public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@smile.cs.tu-berlin.de>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Cc: Phil Edwards <phil@jaj.com>
Subject: preprocessor/8602: incorrect line numbers in warning messages when using inline functions
Date: Fri, 22 Nov 2002 07:42:00 -0000 [thread overview]
Message-ID: <E18Czfz-0001gD-00@smile.cs.tu-berlin.de> (raw)
>Number: 8602
>Category: preprocessor
>Synopsis: incorrect line numbers in warning messages when using inline functions
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Nov 16 02:06:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Andrew Suffield <asuffield@debian.org>
>Release: 3.2.1 (Debian) (Debian unstable)
>Organization:
The Debian Project
>Environment:
System: Debian GNU/Linux (unstable)
Architecture: i686
host: i386-linux
Configured with: /home/packages/gcc/3.2/gcc-3.2-3.2.1ds5/src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-objc-gc i386-linux
>Description:
[ Reported to the Debian BTS as report #153965.
Please CC 153965@bugs.debian.org on replies.
Log of report can be found at http://bugs.debian.org/153965 ]
-----
static inline int
foo(int x)
{
if (!x)
return 0;
}
int main(void)
{
foo(1);
return 1;
}
-----
$ gcc-2.95 -Wall -c !$
gcc-2.95 -Wall -c bug-153965.c
bug-153965.c: In function `foo':
bug-153965.c:6: warning: control reaches end of non-void function
^^^
$ gcc-3.2 -Wall -c bug-153965.c
bug-153965.c: In function `foo':
bug-153965.c:13: warning: control reaches end of non-void function
^^^^
$ gcc-3.3 -Wall -c bug-153965.c
bug-153965.c: In function `foo':
bug-153965.c:13: warning: control reaches end of non-void function
^^^^^
gcc 3.[23] also produces correct line numbers if either "static" or
"inline" is removed from foo. Removing the body of function foo()
causes a secondary warning to be generated in the right place, but the
original warning still has the wrong line number.
[gcc-3.2 is gcc-3.2.1 20021111, gcc-3.3 is HEAD 20021103]
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2002-11-16 10:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E18Czfz-0001gD-00@smile.cs.tu-berlin.de \
--to=doko@smile.cs.tu-berlin.de \
--cc=153965@bugs.debian.org \
--cc=debian-gcc@lists.debian.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=phil@jaj.com \
/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).