public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: gcc-patches Patches <gcc-patches@gcc.gnu.org>
Subject: fix testsuite/48506
Date: Sat, 09 Apr 2011 00:01:00 -0000	[thread overview]
Message-ID: <4AD5EDE8-FA87-4DB7-86CE-A3387389ED8D@comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 116 bytes --]

I've checked in this to avoid problems with ports that default to -fno-common.  I've also checked it into 4.6.x.


[-- Attachment #2: ccp.diffs.txt --]
[-- Type: text/plain, Size: 437 bytes --]

	PR testsuite/48506
	* gcc.dg/tree-ssa/ssa-ccp-17.c: Robustify against ports that
	default to fno-common.

Index: gcc.dg/tree-ssa/ssa-ccp-17.c
===================================================================
--- gcc.dg/tree-ssa/ssa-ccp-17.c	(revision 172125)
+++ gcc.dg/tree-ssa/ssa-ccp-17.c	(working copy)
@@ -18,7 +18,7 @@
   return ((struct Foo *)p)->i;
 }
 
-const struct Foo g;
+extern const struct Foo g;
 
 int foobar(void)
 {

                 reply	other threads:[~2011-04-09  0:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AD5EDE8-FA87-4DB7-86CE-A3387389ED8D@comcast.net \
    --to=mikestump@comcast.net \
    --cc=gcc-patches@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).