public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/39497] dfp.c:239: warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules Date: Wed, 18 Mar 2009 21:24:00 -0000 [thread overview] Message-ID: <20090318212414.23890.qmail@sourceware.org> (raw) In-Reply-To: <bug-39497-682@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2009-03-18 21:24 ------- A patch to build dfp.c with -fno-strict-aliasing is pre-approved (just use the dfp.o-warn variable in Makefile.in) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39497
next prev parent reply other threads:[~2009-03-18 21:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-18 21:13 [Bug middle-end/39497] New: " hjl dot tools at gmail dot com 2009-03-18 21:14 ` [Bug bootstrap/39497] " hjl dot tools at gmail dot com 2009-03-18 21:16 ` [Bug middle-end/39497] " pinskia at gcc dot gnu dot org 2009-03-18 21:24 ` rguenth at gcc dot gnu dot org [this message] 2009-03-18 21:34 ` rguenth at gcc dot gnu dot org 2009-03-24 15:37 ` rguenth at gcc dot gnu dot org 2009-03-25 12:01 ` rguenth at gcc dot gnu dot org 2009-03-25 12:01 ` rguenth 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=20090318212414.23890.qmail@sourceware.org \ --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: linkBe 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).