public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/34716] application segfaults when compiled with -O2, but works well with -O1
Date: Mon, 04 Aug 2014 10:43:00 -0000 [thread overview]
Message-ID: <bug-34716-4-Y8fV0PUhug@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-34716-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34716
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2014-08-04
CC| |ktietz at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #7 from Kai Tietz <ktietz at gcc dot gnu.org> ---
As 5.1 is now already for some time no more in maintenance it would be
interesting to learn if that problem is still there for more current version
(4.9, 4.8) gcc.
next parent reply other threads:[~2014-08-04 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-34716-4@http.gcc.gnu.org/bugzilla/>
2014-08-04 10:43 ` ktietz at gcc dot gnu.org [this message]
2014-08-04 10:44 ` ktietz at gcc dot gnu.org
2008-01-08 19:29 [Bug rtl-optimization/34716] New: " aleksey dot shipilev at gmail dot com
2008-01-08 19:36 ` [Bug rtl-optimization/34716] " aleksey dot shipilev at gmail dot com
2008-01-08 19:58 ` pinskia at gcc dot gnu dot org
2008-01-08 20:07 ` aleksey dot shipilev at gmail dot com
2008-01-08 21:21 ` aleksey dot shipilev at gmail dot com
2008-01-08 21:22 ` pinskia at gcc dot gnu dot org
2008-01-08 21:23 ` aleksey dot shipilev at gmail 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=bug-34716-4-Y8fV0PUhug@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).