This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: HORRIBLE inliner defaillance
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: Paolo Carlini <pcarlini at suse dot de>, gcc at gcc dot gnu dot org, jh at suse dot de, roger at eyesopen dot com, jlquinn at optonline dot net
- Date: 27 Oct 2003 05:53:13 +0100
- Subject: Re: HORRIBLE inliner defaillance
- Organization: Integrable Solutions
- References: <3F99510B.60807@suse.de> <20031024121737.1de79765.bkoz@redhat.com>
Benjamin Kosnik <bkoz@redhat.com> writes:
| >following up to Jerry heads up of a while ago
| >(http://gcc.gnu.org/ml/libstdc++/2003-02/msg00056.html) I really
| >would like to have some feedback from the compiler people about
| >this horrible thing.
|
| See:
| http://gcc.gnu.org/ml/libstdc++/2003-02/msg00302.html
| (This is what should be linked in the TODO, sorry)
Yes, this is the third time I'm seeing pointers to that message and
I'll repeat what I've said a second time: It does nto work. As RTH
said, it is a problem with the inliner. Random "const" will not fix
it. The reason is that toplevel "const" get lost very quickly.
-- Gaby