** Bug watch added: GCC Bugzilla #66425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/305176
Title:
[PR25509] can't disable
** Changed in: gcc-defaults (Ubuntu)
Status: Triaged = Fix Released
** Changed in: glibc (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/305176
Launchpad has imported 28 comments from the remote bug at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25509.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Branch linked: lp:debian/sid/gnat-4.4
--
[PR25509] can't disable __attribute__((warn_unused_result))
https://bugs.launchpad.net/bugs/305176
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: glibc
Status: Confirmed = Fix Released
--
[PR25509] can't disable __attribute__((warn_unused_result))
https://bugs.launchpad.net/bugs/305176
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
It is possible to turn off this warning! Just turn off all
optimizations :(
If you pass -O0, this program doesn't warn. If you pass -O1 or -O2, ...
the program warns.
This is especially bad for things that used to build with -Wall.
--
[PR25509] can't disable
As I said in the edited bug description, -U_FORTIFY_SOURCE works too.
--
[PR25509] can't disable __attribute__((warn_unused_result))
https://bugs.launchpad.net/bugs/305176
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I agree that this warning is sometimes excessive and inconvenient,
particularly for logging writes which are, as you put it, fire and
forget.
Notwithstanding that, though, I would note that it *is* good practice to
check non-logging writes. Contrary to popular belief, write() is not
guaranteed to
On Wed, Jan 21, 2009 at 8:11 AM, Colin Watson cjwat...@canonical.com wrote:
I agree that this warning is sometimes excessive and inconvenient,
particularly for logging writes which are, as you put it, fire and
forget.
Notwithstanding that, though, I would note that it *is* good practice to
** Changed in: glibc
Status: Unknown = Confirmed
--
[PR25509] can't disable __attribute__((warn_unused_result))
https://bugs.launchpad.net/bugs/305176
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
While this doesn't solve the issue of needing a -Wno-warn-unused-
result, or the lack of warnings on fprintf, it may help to disable the
pre-processor option causing the warnings to be used
(-D_FORTIFY_SOURCE=2). If you want to risk losing the other compile-
time and run-time protections, you can
11 matches
Mail list logo
