From: Andrew Cagney <cagney@gnu.org>
To: fnf@ninemoons.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Outwit compiler dead code elimination in break.exp test (revised patch)
Date: Mon, 08 Dec 2003 00:31:00 -0000 [thread overview]
Message-ID: <3FD3C665.4090603@gnu.org> (raw)
In-Reply-To: <200312071421.17200.fnf@ninemoons.com>
> On Monday 01 December 2003 10:52, Andrew Cagney wrote:
>
>> As for stopping GCC from eliminating code - last time this came up (ref
>> store.exp) it was recommended that the .c files be split so that GCC
>> couldn't see the potential optimization.
>
>
> OK. I've revised the patch to split the source file. This is
> pretty ugly though as there are a half dozen tests that have
> to be modified to accomodate two source files.
>
> I've attached the patch for review/approval.
Wow, thanks for doing this! I was thinking that just one test needed
changes. Anyway, perhaphs wait for michaelc to put it through his test
harness before committing.
Andrew
next prev parent reply other threads:[~2003-12-08 0:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 23:05 [PATCH] Outwit compiler dead code elimination in break.exp test Fred Fish
2003-11-30 1:04 ` Fred Fish
2003-11-30 1:07 ` Daniel Jacobowitz
2003-11-30 1:26 ` Fred Fish
2003-12-01 0:46 ` Fred Fish
2003-12-01 14:58 ` Elena Zannoni
2003-12-01 15:30 ` Fred Fish
2003-12-01 15:46 ` Elena Zannoni
2003-12-01 16:39 ` Fred Fish
2003-12-01 14:23 ` Elena Zannoni
2003-12-01 14:44 ` Daniel Jacobowitz
2003-12-01 17:52 ` Andrew Cagney
2003-12-01 18:10 ` Fred Fish
2003-12-09 1:02 ` Michael Snyder
2003-12-07 21:21 ` [PATCH] Outwit compiler dead code elimination in break.exp test (revised patch) Fred Fish
2003-12-08 0:31 ` Andrew Cagney [this message]
2003-12-08 4:20 Michael Elizabeth Chastain
2003-12-08 23:49 ` Andrew Cagney
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=3FD3C665.4090603@gnu.org \
--to=cagney@gnu.org \
--cc=fnf@ninemoons.com \
--cc=gdb-patches@sources.redhat.com \
/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