public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Cc: Richard Sandiford <richard@codesourcery.com>,  nathan@codesourcery.com
Subject: Re: Fix gcc.c-torture/execute/20030928-1.c for ARM VxWorks
Date: Sat, 14 Jul 2007 03:43:00 -0000	[thread overview]
Message-ID: <200707140246.07212.paul@codesourcery.com> (raw)
In-Reply-To: <87hcokh4si.fsf@firetop.home>

On Wednesday 04 July 2007, Richard Sandiford wrote:
> This patch fixes gcc.c-torture/execute/20030928-1.c for ARM VxWorks
> kernels.  We tried to create "symbol + big offset" constants, which
> runs into the problems described in the patch.

This seems like something there should be a target independent knob for. 
Apparently there isn't though, so ok.

Paul

  parent reply	other threads:[~2007-07-14  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04 10:01 Richard Sandiford
2007-07-11  2:51 ` Mark Mitchell
2007-07-14  3:43 ` Paul Brook [this message]
     [not found] ` <1184921014.32244.0.camel@pc960.cambridge.arm.com>
2007-07-20 10:24   ` Richard Sandiford

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=200707140246.07212.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nathan@codesourcery.com \
    --cc=richard@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).