public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38616] [4.3 Regression] Wrong code when -O3 or -O2 -fstack-protector used
Date: Wed, 14 Jan 2009 19:24:00 -0000 [thread overview]
Message-ID: <20090114192402.12526.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38616-17114@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from pinskia at gcc dot gnu dot org 2009-01-14 19:24 -------
>/mnt/gnu/gcc/gcc/gcc/testsuite/gcc.dg/pr38616.c:1: warning: -fstack-protector
That has already been fixed:
http://gcc.gnu.org/ml/gcc-cvs/2009-01/msg00372.html
Fixed so closing.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38616
next prev parent reply other threads:[~2009-01-14 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 11:53 [Bug c/38616] New: Wrong code when -O3 or -O2 used socketpair at gmail dot com
2008-12-24 13:28 ` [Bug c/38616] " socketpair at gmail dot com
2008-12-24 13:35 ` socketpair at gmail dot com
2008-12-24 13:41 ` socketpair at gmail dot com
2008-12-24 13:59 ` [Bug middle-end/38616] [4.3 only] Wrong code when -O3 or -O2 -fstack-protector used pinskia at gcc dot gnu dot org
2008-12-24 15:23 ` socketpair at gmail dot com
2008-12-24 15:29 ` socketpair at gmail dot com
2008-12-29 20:39 ` [Bug middle-end/38616] [4.3 Regression] " rguenth at gcc dot gnu dot org
2009-01-11 17:29 ` doko at gcc dot gnu dot org
2009-01-11 17:38 ` doko at gcc dot gnu dot org
2009-01-14 19:18 ` danglin at gcc dot gnu dot org
2009-01-14 19:24 ` pinskia at gcc dot gnu dot org [this message]
2009-01-18 17:08 ` hjl dot tools at gmail dot com
2009-01-18 22:06 ` hjl dot tools 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=20090114192402.12526.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: 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).