public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tg at mirbsd dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/30477] Integer Overflow detection code optimised away, -fwrapv broken Date: Tue, 16 Jan 2007 03:40:00 -0000 [thread overview] Message-ID: <20070116033951.3557.qmail@sourceware.org> (raw) In-Reply-To: <bug-30477-13924@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from tg at mirbsd dot de 2007-01-16 03:39 ------- Subject: Re: Integer Overflow detection code optimised away, -fwrapv broken pinskia at gmail dot com dixit: >If you consider 4.0.x I didn't say anything about 4.0, just gcc4 instead of gcc3. And many people (e.g. most embedded systems developers or persons with a large legacy codebase) just can't easily upgrade. >Right but 3.4.x is no longer maintained. This is like any other project >where old versions are no longer maintained. Ask for an example Mozilla Just that, in my opinion, core technology like especially gcc which changes over time (in contrast to binutils, where it pretty much doesn't matter if you upgrade) should be taken with a little bit more effort, especially if it's used by SO many people. >So how long do you support a release branch of your OS? We are two persons, thus, releases are more like snapshots that are especially stable. We do backport relevant changes if desired by users, though. >> Especially you as the author of code in question >I did not write this code, I just know of it. You did: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27257#c2 >So it is a trade off, break existing code or go by the standard. We I'm actually for "go by the standard", but, like I said, core technology, legacy codebase, should deserve a little bit more attention, especially if it's security relevant. Hey, I mean, is -fwrapv not actually supposed to counter this specific optimisation? bye, //mirabile -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30477
next prev parent reply other threads:[~2007-01-16 3:40 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-15 23:43 [Bug c/30477] New: " tg at mirbsd dot org 2007-01-15 23:56 ` [Bug c/30477] " pinskia at gcc dot gnu dot org 2007-01-15 23:57 ` pinskia at gcc dot gnu dot org 2007-01-16 2:34 ` tg at mirbsd dot org 2007-01-16 3:04 ` pinskia at gmail dot com 2007-01-16 3:40 ` tg at mirbsd dot de [this message] 2007-01-16 3:48 ` Andrew Pinski 2007-01-16 3:49 ` pinskia at physics dot uc dot edu 2007-01-16 4:08 ` tg at mirbsd dot org 2007-01-16 10:36 ` rguenth at gcc dot gnu dot org 2007-01-16 16:56 ` tg at mirbsd dot org 2007-01-16 17:18 ` rguenth at gcc dot gnu dot org 2007-01-16 17:34 ` tg at mirbsd dot org 2007-01-16 17:49 ` tg at mirbsd dot org 2007-01-16 18:00 ` pinskia at gcc dot gnu dot org 2007-01-16 18:01 ` gdr at cs dot tamu dot edu 2007-01-22 23:54 ` tg at mirbsd dot de 2007-01-25 14:29 ` tg at mirbsd dot org 2007-01-25 14:50 ` rguenth at gcc dot gnu dot org 2007-01-25 16:09 ` tg at mirbsd dot org [not found] <bug-30477-4@http.gcc.gnu.org/bugzilla/> 2014-02-16 13:17 ` jackie.rosen at hushmail dot com
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=20070116033951.3557.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).