public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55591] New: strict-aliasing & Fortran Date: Tue, 04 Dec 2012 11:38:00 -0000 [thread overview] Message-ID: <bug-55591-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55591 Bug #: 55591 Summary: strict-aliasing & Fortran Classification: Unclassified Product: gcc Version: 4.7.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: Joost.VandeVondele@mat.ethz.ch As suggested in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55585#c5 Richard: GFortran could enable strict-aliasing unconditionally if it likes (even at -O0). I think this makes sense given the Fortran semantics and the way people usually code in Fortran. Given this is the default at -O2 already, I think -fstrict-aliasing is well tested.
next reply other threads:[~2012-12-04 11:38 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-04 11:38 Joost.VandeVondele at mat dot ethz.ch [this message] 2012-12-04 13:36 ` [Bug fortran/55591] " rguenth at gcc dot gnu.org 2012-12-04 15:47 ` jvdelisle at gcc dot gnu.org 2012-12-04 17:06 ` burnus at gcc dot gnu.org 2012-12-19 7:48 ` Joost.VandeVondele at mat dot ethz.ch 2013-03-29 6:13 ` Joost.VandeVondele at mat dot ethz.ch 2014-12-21 12:24 ` dominiq at lps dot ens.fr 2014-12-22 7:15 ` Joost.VandeVondele at mat dot ethz.ch
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-55591-4@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: 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).