public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* How to report pch-branch bugs?
@ 2002-12-02  9:56 Karel Gardas
  2003-01-02 18:00 ` Geoff Keating
  0 siblings, 1 reply; 2+ messages in thread
From: Karel Gardas @ 2002-12-02  9:56 UTC (permalink / raw)
  To: GCC Mailing List


Hello,

simply speaking I'm not sure that gcc report bug instruction applies to
pch-branch too while using pch. I.e. I don't think that it would be good
to upload 40MB pch file as a part of bug report.

I've tried to use pch-branch (from todays, bootstraped ok on my Debian
GNU/Linux 3.0) with MICO and it fails with:

thinkpad:~/arch/devel/gcc-pch/orb$ time make
c++  -I../include -DFAST_PCH   -Wall -fpermissive    -DPIC -fPIC  -c os-unix.cc -o os-unix.pic.o
/home/karel/usr/local/pch-branch/include/c++/3.3/bits/list.tcc: In
instantiation of `std::list<MICO::UnixProcess*,
std::allocator<MICO::UnixProcess*> >':
os-unix.cc:71:   instantiated from here
/home/karel/usr/local/pch-branch/include/c++/3.3/bits/list.tcc:131:
internal compiler error: in
   grok_op_properties, at cp/decl.c:12675
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make: *** [os-unix.pic.o] Error 1

Switch -DFAST_PCH directs compiler to include file orb_pch.h which
includes all header files included in files of this (orb) directory. I've
compiled this file before with exactly the same options.

Actual code of cc files looks:

#ifdef FAST_PCH
#include "orb_pch.h"
#endif // FAST_PCH
#ifdef __COMO__
#pragma hdrstop
#endif // __COMO__

#ifndef FAST_PCH

// all other includes of certain files

#endif // FAST_PCH


Anything other I should provide?

Thanks,

Karel
--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: How to report pch-branch bugs?
  2002-12-02  9:56 How to report pch-branch bugs? Karel Gardas
@ 2003-01-02 18:00 ` Geoff Keating
  0 siblings, 0 replies; 2+ messages in thread
From: Geoff Keating @ 2003-01-02 18:00 UTC (permalink / raw)
  To: Karel Gardas; +Cc: gcc

Karel Gardas <kgardas@objectsecurity.com> writes:

> Hello,
> 
> simply speaking I'm not sure that gcc report bug instruction applies to
> pch-branch too while using pch. I.e. I don't think that it would be good
> to upload 40MB pch file as a part of bug report.

No, please don't.  I've updated the bug reporting instructions.  The
bug you reported has most likely been fixed on pch-branch, please try
again.

> /home/karel/usr/local/pch-branch/include/c++/3.3/bits/list.tcc: In
> instantiation of `std::list<MICO::UnixProcess*,
> std::allocator<MICO::UnixProcess*> >':
> os-unix.cc:71:   instantiated from here
> /home/karel/usr/local/pch-branch/include/c++/3.3/bits/list.tcc:131:
> internal compiler error: in
>    grok_op_properties, at cp/decl.c:12675
-- 
- Geoffrey Keating <geoffk@geoffk.org>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-01-02 18:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-12-02  9:56 How to report pch-branch bugs? Karel Gardas
2003-01-02 18:00 ` Geoff Keating

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