public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/4890: inconsistent int-to-pointer warning
Date: Wed, 06 Nov 2002 04:46:00 -0000	[thread overview]
Message-ID: <20021106124605.9023.qmail@sources.redhat.com> (raw)

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

From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
  nobody@gcc.gnu.org, gsicherm@elity.com
Cc:  
Subject: Re: c/4890: inconsistent int-to-pointer warning
Date: Wed, 6 Nov 2002 13:38:40 +0100

 Hi,
 
 I can confirm that this is still present in gcc-3.2. I can't reproduce
 with recent 3.3, don't know about 3.2.1 yet. The problem is not arch
 specific.
 
 Here are instructions on how to reproduce this with a much smaller
 testcase:
 
 touch /usr/include/empty.h
 echo '#include <empty.h>' >t.c
 gcc -traditional -E t.c
 # 1 "p.c"
 # 1 "/usr/include/empty.h" 1 3
 # 2 "p.c" 2 3
 
 The last line is the problem: ``# 2 "p.c 2 3'' means:
                                   ^  ^   ^ ^
                                   |  |   | |
 New line number is 2 -------------+  |   | |
 New file name is p.c ----------------+   | |
 Event was LC_LEAVE   --------------------+ |
 We are returning to SYSTEM header ---------+
 
 The last part is clearly wrong. Also this is a regression from 2.95.3
 
     regards   Christian
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4890
 
 -- 
 THAT'S ALL FOLKS!


                 reply	other threads:[~2002-11-06 12:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021106124605.9023.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --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).