public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: debug/9905: [3.4 regression] Unhandled STMT_EXPR in loc_descriptor_from_tree
Date: Thu, 20 Mar 2003 14:26:00 -0000	[thread overview]
Message-ID: <20030320142600.2897.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

The following reply was made to PR debug/9905; it has been noted by GNATS.

From: Andreas Schwab <schwab@suse.de>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:  
Subject: Re: debug/9905: [3.4 regression] Unhandled STMT_EXPR in
 loc_descriptor_from_tree
Date: Thu, 20 Mar 2003 15:16:10 +0100

 loc_descriptor_from_tree also does not handle MODIFY_EXPR (also triggered
 by glibc):
 
 $ cat modify.c
 int main ()
 {
   int n;
   int k[n = 1];
 }
 $ gcc -g modify.c 
 modify.c: In function `main':
 modify.c:5: internal compiler error: in loc_descriptor_from_tree, at dwarf2out.c:8962
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 -- 
 Andreas Schwab, SuSE Labs, schwab@suse.de
 SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
 Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
 "And now for something completely different."


             reply	other threads:[~2003-03-20 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 14:26 Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-11 11:26 Steven Bosscher
2003-03-16 18:56 Andreas Schwab
2003-03-14 21:32 bangerth

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=20030320142600.2897.qmail@sources.redhat.com \
    --to=schwab@suse.de \
    --cc=gcc-prs@gcc.gnu.org \
    --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).