public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aviro at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/29970] mixing ({...}) with VLA leads to massive breakage
Date: Fri, 24 Nov 2006 15:25:00 -0000 [thread overview]
Message-ID: <20061124152514.8517.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29970-13620@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from aviro at redhat dot com 2006-11-24 15:25 -------
27301 looks similar to what the first one trips, but passing pointers
as suggested by #3 there is not a panacea - testcases 4 and 5
actually deal with that variant. It really looks as if part (but not
all) information about the type dies when we leave the scope and
we end up stepping into that when working with object afterwards.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29970
next prev parent reply other threads:[~2006-11-24 15:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 12:36 [Bug c/29970] New: " aviro at redhat dot com
2006-11-24 13:57 ` [Bug c/29970] " joseph at codesourcery dot com
2006-11-24 15:25 ` aviro at redhat dot com [this message]
2006-11-25 1:55 ` pinskia at gcc dot gnu dot org
[not found] <bug-29970-4@http.gcc.gnu.org/bugzilla/>
2021-03-23 19:33 ` pinskia at gcc dot gnu.org
2021-03-23 19:45 ` tunagul29 at icloud dot com
2021-08-03 18:12 ` muecker at gwdg dot de
2021-08-05 18:25 ` muecker at gwdg dot de
2021-08-10 5:50 ` cvs-commit at gcc dot gnu.org
2021-08-12 18:37 ` cvs-commit at gcc dot gnu.org
2021-08-14 20:03 ` muecker at gwdg dot de
2021-09-04 19:55 ` muecker at gwdg dot de
2021-09-05 19:16 ` muecker at gwdg dot de
2021-11-07 11:57 ` muecker at gwdg dot de
2021-11-17 13:30 ` cvs-commit at gcc dot gnu.org
2023-05-31 2:20 ` egallager at gcc dot gnu.org
2023-05-31 5:01 ` muecker at gwdg dot de
2024-01-26 1:01 ` gabravier at gmail dot com
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=20061124152514.8517.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: 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).