public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
To: Phil Edwards <phil@jaj.com>
Cc: <gcc@gcc.gnu.org>, Mark Mitchell <mark@codesourcery.com>
Subject: Re: Another new-parser problem? (libstdc++)
Date: Fri, 17 Jan 2003 19:09:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0301171713010.19303-101000@bellatrix.tat.physik.uni-tuebingen.de> (raw)
In-Reply-To: <20030117103207.A26897@disaster.jaj.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2136 bytes --]

Ok, a "simple" testcase is attached (unincluded output from -save-temps
.ii file, line-numbers and blank lines removed, etc.). To reproduce
simply do

> g++ -c CompressibleBlock.ii.h

Hope this helps,

   Richard.

On Fri, 17 Jan 2003, Phil Edwards wrote:

> On Fri, Jan 17, 2003 at 11:26:29AM +0100, Richard Guenther wrote:
> > Hi!
> >
> > Does the following look familiar to anyone? (with todays mainline)
> >
> > /home/rguenth/ix86/gcc3.4/include/c++/3.4/bits/stl_vector.h: In
> > instantiation of `std::_Vector_alloc_base<Observer<T*>*, std::allocator<Observer<T*>*>,
> > std::_Alloc_traits<Observer<T*>*, std::allocator<Observer<T*>*> >::_S_instanceless>':
> > /net/bellatrix/home/rguenth/src/pooma-bugfixes/r2/src/Utilities/Observable.h:236:
> > instantiated from `std::_Vector_base<Observer<T*>*, std::allocator<Observer<T*>*> >'
> > /net/bellatrix/home/rguenth/src/pooma-bugfixes/r2/src/Utilities/Observable.h:236:
> > instantiated from `std::vector<Observer<T*>*, std::allocator<Observer<T*>*> >'
> > /net/bellatrix/home/rguenth/src/pooma-bugfixes/r2/src/Utilities/Observable.h:236:
> > instantiated from `Observable<T*>'
> > /net/bellatrix/home/rguenth/src/pooma-bugfixes/r2/src/Engine/CompressibleBlock.h:742:
> >   instantiated from here
> > /home/rguenth/ix86/gcc3.4/include/c++/3.4/bits/stl_vector.h:91: error: `
> >    std::_Vector_alloc_base<_Tp, _Allocator, _IsStatic>::_M_data_allocator'
> > has incomplete type
> > /home/rguenth/ix86/gcc3.4/include/c++/3.4/bits/stl_vector.h:91: confused
> > by earlier errors, bailing out
>
> I don't see that, but I'm getting compiler segfaults during the normal build.
> Going into the library builddir and running 'make' works (it doesn't pass
> -O2 in this case).
>
> > I did look at the stl_vector.h part and the _Alloc_traits template, but
> > nothing obvious seems to be wrong...
>
> I'm guessing some possible fallout from the removal of the implicit typename
> extension... I've seen some odd errors in the last 48 hours about lookups
> of base members.
>
> Phil

--
Richard Guenther <richard.guenther@uni-tuebingen.de>
WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/

[-- Attachment #2: testcase --]
[-- Type: APPLICATION/octet-stream, Size: 8637 bytes --]

  reply	other threads:[~2003-01-17 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-17 16:26 Richard Guenther
2003-01-17 18:40 ` Phil Edwards
2003-01-17 19:09   ` Richard Guenther [this message]
2003-01-17 20:03     ` Mark Mitchell
2003-01-21 19:10       ` Richard Guenther
2003-01-21 20:23       ` Richard Guenther

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=Pine.LNX.4.33.0301171713010.19303-101000@bellatrix.tat.physik.uni-tuebingen.de \
    --to=rguenth@tat.physik.uni-tuebingen.de \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=phil@jaj.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).