This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/45249] Indirect variable parameters sometimes cause segmentation fault
- From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 Aug 2010 20:33:05 -0000
- Subject: [Bug c++/45249] Indirect variable parameters sometimes cause segmentation fault
- References: <bug-45249-19547@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #29 from rguenth at gcc dot gnu dot org 2010-08-11 20:33 -------
(In reply to comment #28)
> (In reply to comment #23)
> > First off I already mentioned what is undefined in this example in comment #11.
> > The part of the standard that mentions about arrays. And how the address of a
> > scalar is considered an array of size 1. I don't have the standard in front of
> > me right now but those are what I remember from the standard.
>
>
> Right. And I clearly explained in my comment #14 why you were wrong. Getting
> back to comment #11 so that we can run around in circles brings no improvement
> to this conversation, and you will just keep on being wrong, even if you had
> the standard in front of you, because your example in comment #11 does not
> correspond to the code I'm doing. My comment #14 explains what is the correct
> code for comparison.
We're indeed running in circles. Maybe you can find someone that can explain
to you better on comp.lang.c.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45249