public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@redhat.com
To: gcc-gnats@gcc.gnu.org
Cc: geoffk@apple.com
Subject: other/9472: [pch] error when creating pch still causes output
Date: Tue, 28 Jan 2003 03:46:00 -0000	[thread overview]
Message-ID: <20030128034118.25638.qmail@sources.redhat.com> (raw)


>Number:         9472
>Category:       other
>Synopsis:       [pch] error when creating pch still causes output
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 28 03:46:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Benjamin Kosnik
>Release:        rh 7.3, head
>Organization:
>Environment:
Reading specs from /mnt/hd/ahimsa/bld-x86-gcc/gcc/specs
Configured with: /mnt/hd/bliss/src.gcc/gcc/configure --prefix=/mnt/hd/ahimsa/H-x86-gcc --enable-languages=c,c++ --enable-__cxa_atexit
Thread model: posix
gcc version 3.4 20030126 (experimental)
>Description:

Create a bogus C++ header, try to precompile it. You'll get a warning, AND a .pch file.

This is entirely unexpected: if gcc can't compile a file, it does not then write out an invalid .o file.

>How-To-Repeat:

%COMP.sh "-x c++-header -Winvalid-pch" ostream

/mnt/hd/ahimsa/bld-x86-gcc/i686-pc-linux-gnu/libstdc++-v3/include/bits/stl_algobase.h:149: warning: inline
   function `const _Tp& std::min(const _Tp&, const _Tp&) [with _Tp = size_t]' 
   used but never defined
/usr/lib/crt1.o(.text+0x18): In function `_start':
: undefined reference to `main'
collect2: ld returned 1 exit status

%ll ostream.pch 
-rw-rw-r--    1 bkoz     bkoz         7.0M Jan 27 21:37 ostream.pch
>Fix:
Don't write out the file.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-01-28  3:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28  3:46 bkoz [this message]
2003-01-28  8:02 paolo

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=20030128034118.25638.qmail@sources.redhat.com \
    --to=bkoz@redhat.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=geoffk@apple.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).