public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11078] [ABI] ICE in write_type with typeof and templates Date: Mon, 09 Aug 2004 17:31:00 -0000 [thread overview] Message-ID: <20040809173156.31433.qmail@sourceware.org> (raw) In-Reply-To: <20030603112812.11078.jtotland1@chello.no> ------- Additional Comments From gdr at integrable-solutions dot net 2004-08-09 17:31 ------- Subject: Re: [ABI] ICE in write_type with typeof and templates "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org> writes: | I went and read the docs, and still fail to see how it can be useful. But you | have a point in that we cannot probably drop support for it so easily. | | What about stripping out typeof(type) while mangling, then? It really does not | buy us anything. Plus, I don't think we want to say that the following | declarations are declaring two different functions: | | void foo(typeof(int*)); | void foo(int*); | | or these: | | void bar(typeof(typeof(char*) [4]) blah); | void bar(char *blah[4]); As I said before, the problem is inexistent for ordinary functions because we don't care about the retun type of those. The issue is with function templates, and there we do care. So I don't believe in arguments based on ordinary functions to strip out typeof. | | In other words, we can easily strip typeof(type) while mangling, and encoding | typeof(expr) as Y <expression> E. | | If we agree on this, I don't think we reach a conclusion based on the arguments you developed above. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11078
next prev parent reply other threads:[~2004-08-09 17:31 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-06-03 11:28 [Bug c++/11078] New: typeof and templates.... internal compiler error jtotland1@chello.no 2003-06-03 12:03 ` [Bug c++/11078] ICE with typeof and templates reichelt@gcc.gnu.org 2003-06-14 23:41 ` [Bug c++/11078] ICE in write_type " pinskia@physics.uc.edu 2003-07-20 3:20 ` pinskia at physics dot uc dot edu 2003-07-30 15:12 ` gccbugs at contacts dot eelis dot net 2003-07-30 15:30 ` reichelt at igpm dot rwth-aachen dot de 2003-08-23 0:24 ` dhazeghi at yahoo dot com 2003-09-25 1:33 ` bangerth at dealii dot org 2004-07-26 13:33 ` pinskia at gcc dot gnu dot org 2004-07-31 1:18 ` [Bug c++/11078] [ABI] " giovannibajo at libero dot it 2004-07-31 10:26 ` giovannibajo at libero dot it 2004-07-31 17:33 ` gdr at integrable-solutions dot net 2004-08-03 20:57 ` ian at wasabisystems dot com 2004-08-03 21:28 ` boris at kolpackov dot net 2004-08-03 21:40 ` bangerth at dealii dot org 2004-08-09 2:40 ` giovannibajo at libero dot it 2004-08-09 13:56 ` ian at wasabisystems dot com 2004-08-09 14:14 ` gdr at integrable-solutions dot net 2004-08-09 14:39 ` giovannibajo at libero dot it 2004-08-09 14:47 ` ian at wasabisystems dot com 2004-08-09 15:05 ` giovannibajo at libero dot it 2004-08-09 17:11 ` gdr at integrable-solutions dot net 2004-08-09 17:31 ` gdr at integrable-solutions dot net [this message] 2004-08-10 0:49 ` giovannibajo at libero dot it 2004-08-10 1:35 ` gdr at integrable-solutions dot net 2004-11-10 2:00 ` pinskia at gcc dot gnu dot org [not found] <bug-11078-6207@http.gcc.gnu.org/bugzilla/> 2005-12-23 15:52 ` pinskia at gcc dot gnu dot org 2007-05-12 13:44 ` pinskia at gcc dot gnu dot org 2007-05-15 1:36 ` blaisorblade_spam at yahoo dot it
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=20040809173156.31433.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).