From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Back branches vs. gcc 4.8.0 |
Date: | 2013-04-05 22:28:03 |
Message-ID: | CAM3SWZR1ZUesm3+okAZcmuKy+edxRP0cxE7QR5x_81jGfL9Kng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 5, 2013 at 11:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It also strikes me that we ought to take this as a warning sign
> that we need to work on getting rid of coding like the above in favor
> of genuine "flexible arrays", before the gcc boys think of some other
> overly-cute optimization based on the assumption that an array declared
> with a fixed size really is fixed.
The traditional argument against that has been that that's a C99
feature. However, since it appears that even MSVC supports flexible
arrays (which are described as a "Microsoft extension", so may not
have identical semantics), it might be possible to do this across the
board without contorting the code with preprocessor hacks. That's
something that I'd certainly be in favor of pursuing.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Flower | 2013-04-05 22:29:12 | Re: Back branches vs. gcc 4.8.0 |
Previous Message | Rodrigo Barboza | 2013-04-05 22:26:49 | Unrecognized type error (postgres 9.1.4) |