public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	martin.dorey@bluearc.com, nobody@gcc.gnu.org
Subject: Re: c++/8332: strlen/template interaction causes ICE
Date: Mon, 28 Oct 2002 13:27:00 -0000	[thread overview]
Message-ID: <20021028212746.30829.qmail@sources.redhat.com> (raw)

Synopsis: strlen/template interaction causes ICE

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Mon Oct 28 13:27:44 2002
State-Changed-Why:
    I _can_ reproduce this. The bug goes away, if strlen is 
    renamed, or if its return type is changed to "int", so I
    assume this has something to do with built-ins. However,
    since the code also SegFaults if we include <string.h>, I
    have no reason to believe that this code is wrong. I'd think
    this is a serious regression from previous releases!
    
    For more information: the SegFault occurs here:
    #0  write_builtin_type (type=0x0) at ../../gcc-3.2/gcc/cp/mangle.c:1569
    #1  0x080bbfc5 in write_type (type=0x401888c0)
        at ../../gcc-3.2/gcc/cp/mangle.c:1399
    #2  0x080bc8df in write_template_args (args=0x4019ec80)
        at ../../gcc-3.2/gcc/cp/mangle.c:1789
    #3  0x080bb13f in write_name (decl=0x401aac40, ignore_local_scope=0)
        at ../../gcc-3.2/gcc/cp/mangle.c:719
    #4  0x080bafd3 in write_encoding (decl=0x401aac40)
        at ../../gcc-3.2/gcc/cp/mangle.c:654
    #5  0x080bd586 in mangle_decl_string (decl=0x401aac40)
        at ../../gcc-3.2/gcc/cp/mangle.c:630
    
    The code in question is
          /* TYPE may still be wchar_t, since that isn't in
    	 integer_type_nodes.  */
          if (type == wchar_type_node)
    	write_char ('w');
          else if (TYPE_FOR_JAVA (type))     <<<<< here
    	write_java_integer_type_codes (type);
          else
    and the reason is that type==0. On one frame higher, this
    code is called from
    	  write_builtin_type (TYPE_MAIN_VARIANT (type));
    Here, type is still!=0, but given the nesting of macros,
    this is the point where I leave the rest to someone else.
    
    Regards
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8332


             reply	other threads:[~2002-10-28 21:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 13:27 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-07 15:26 Wolfgang Bangerth
2002-10-23 22:06 Andrew Pinski
2002-10-23 21:46 martin.dorey

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=20021028212746.30829.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=martin.dorey@bluearc.com \
    --cc=nobody@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: 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).