public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/26021] [4.2 Regression] gcc.c:3866: warning: comparison between signed and unsigned
Date: Tue, 31 Jan 2006 01:04:00 -0000	[thread overview]
Message-ID: <20060131010441.3063.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26021-276@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from dave at hiauly1 dot hia dot nrc dot ca  2006-01-31 01:04 -------
Subject: Re:  [4.2 Regression] gcc.c:3866: warning: comparison between signed
and unsigned

> These show up when MODIFY_TARGET_NAME is defined.

This is a macro that I hadn't noticed before.  It seems the PA is
the only port to define it.  The driver options for it don't appear
to be documented.  It was added by Richard Kenner in 2000 at the request
of HP.  I doubt it works very well as the default target names in use
now don't allow the arbitrary addition and removal of 64 to select
between 32 and 64-bit targets.  Thus, I'm wondering whether this macro
shouldn't just be deleted.

I'll ping Steve.

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26021


  parent reply	other threads:[~2006-01-31  1:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29 23:13 [Bug driver/26021] New: " danglin at gcc dot gnu dot org
2006-01-29 23:29 ` [Bug driver/26021] " danglin at gcc dot gnu dot org
2006-01-29 23:31 ` [Bug driver/26021] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-01-29 23:32 ` danglin at gcc dot gnu dot org
2006-01-30  0:41 ` pinskia at gcc dot gnu dot org
2006-01-31  1:04 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2006-02-02  0:09 ` sje at cup dot hp dot com
2006-02-02  1:12 ` dave at hiauly1 dot hia dot nrc dot ca

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=20060131010441.3063.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).