public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cookevillain at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/55422] gcc does not diagnose change of linkage for a function.
Date: Tue, 20 Nov 2012 23:56:00 -0000 [thread overview]
Message-ID: <bug-55422-4-ueGNT1PJ7Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55422-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55422
--- Comment #1 from cookevillain at yahoo dot com 2012-11-20 23:55:16 UTC ---
gcc -v output, omitted in the report:
-------------------------------------
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
4.4.3-4ubuntu5.1' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--enable-multiarch --enable-linker-build-id --with-system-zlib
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls
--enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc
--enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1)
next prev parent reply other threads:[~2012-11-20 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 23:52 [Bug c/55422] New: " cookevillain at yahoo dot com
2012-11-20 23:56 ` cookevillain at yahoo dot com [this message]
2012-11-21 11:30 ` [Bug c/55422] " mpolacek at gcc dot gnu.org
2012-11-21 12:44 ` mpolacek at gcc dot gnu.org
2012-11-21 21:54 ` cookevillain at yahoo dot com
2012-12-09 1:29 ` pinskia at gcc dot gnu.org
2023-12-17 20:51 ` pinskia at gcc dot gnu.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=bug-55422-4-ueGNT1PJ7Y@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).