public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: rask at sygehus dot dk <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug target/30370] Build failure in libgcc2 powitf2 with ICE in  gen_reg_rtx
Date: Sat, 06 Jan 2007 15:08:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0701061505470.21263@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20070106142807.5915.qmail@sourceware.org>

On Sat, 6 Jan 2007, rask at sygehus dot dk wrote:

> Like
> ifneq (,$(findstring gnu,$(target)))
> ifeq (,$(findstring gnuspe,$(target)))
> ...
> endif
> endif
> ?

Yes, just like that.

> How about s/gnuspe/spe/ in case someone comes up with a powerpc-gnufubarspe
> target?

Seems reasonable.

-- 
Joseph S. Myers
joseph@codesourcery.com


  reply	other threads:[~2007-01-06 15:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 19:28 [Bug target/30370] New: [regression] " rask at sygehus dot dk
2007-01-04 20:34 ` [Bug target/30370] " joseph at codesourcery dot com
2007-01-05  5:04 ` [Bug target/30370] " pinskia at gcc dot gnu dot org
2007-01-05 17:29 ` rask at sygehus dot dk
2007-01-05 17:52 ` joseph at codesourcery dot com
2007-01-06 14:28 ` rask at sygehus dot dk
2007-01-06 15:08   ` Joseph S. Myers [this message]
2007-01-06 15:08 ` joseph at codesourcery dot com
2007-01-07 14:07 ` rask at sygehus dot dk
2007-01-07 14:16 ` rask at sygehus dot dk
2007-01-07 23:43 ` drow at gcc dot gnu dot org
2007-01-31  1:20 ` [Bug target/30370] [4.1 regression] " mmitchel at gcc dot gnu dot org
2007-02-02 16:06 ` dje at gcc dot gnu dot org
2007-02-03 17:30 ` jsm28 at gcc dot gnu dot org
2007-02-05  6:05 ` mmitchel at gcc dot gnu dot org
2007-02-05 17:35 ` dje at gcc dot gnu dot org
2007-02-05 19:17 ` mmitchel at gcc dot gnu dot org
2007-02-06 20:51 ` mmitchel at gcc dot gnu dot org
2007-02-06 20:59 ` mmitchel at gcc dot gnu dot org
2007-02-06 21:07 ` mmitchel at gcc dot gnu dot org

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=Pine.LNX.4.64.0701061505470.21263@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).