public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mchen <mchen@transdimension.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/8624: gcc 2.95.3 (arm-linux-gcc) char type problem.
Date: Sat, 23 Nov 2002 04:49:00 -0000	[thread overview]
Message-ID: <20021118201604.4380.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/8624; it has been noted by GNATS.

From: mchen <mchen@transdimension.com>
To: schwab@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   mchen@transdimension.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: target/8624: gcc 2.95.3 (arm-linux-gcc) char type problem.
Date: Mon, 18 Nov 2002 12:09:01 -0800

 Thanks!
 
 schwab@gcc.gnu.org wrote:
 > 
 > Synopsis: gcc 2.95.3 (arm-linux-gcc) char type problem.
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: schwab
 > State-Changed-When: Mon Nov 18 12:03:29 2002
 > State-Changed-Why:
 >     Not a bug, char is unsigned by default on arm.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8624


             reply	other threads:[~2002-11-18 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23  4:49 mchen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-23  1:56 schwab
2002-11-23  1:16 mchen

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=20021118201604.4380.qmail@sources.redhat.com \
    --to=mchen@transdimension.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).