On 05/16/2010 02:05 PM, Bruno Haible wrote:
enum { a, b, c };
int function (int n)
{
extern int (* verify_function5 (void)) [(!!sizeof (struct { unsigned int
verify_error_if_negative_size__: (c == 2) ? 1 : -1; }))];
return 0;
}
What version of GCC? I think you should report it to the
Hi Paolo,
What version of GCC? ...
I cannot reproduce it with either Fedora 12 or upstream GCC 4.5.0.
gcc -v says:
gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE
Linux)
I think you should report it to the suse bugzilla,
I would do so if there was
Hi,
A week ago, Jim wrote:
+ init.sh: enable MALLOC_PERTURB_
+ * tests/init.sh: Enable glibc's malloc-perturbing option.
This triggers a SKIP for test-verify.sh on openSUSE Linux 11.0 systems:
test-verify.sh: skipped test: cannot compile error-free
SKIP: test-verify.sh
The reason
On Sun, May 09, 2010 at 10:47:07PM +0200, Jim Meyering wrote:
+# Enable glibc's malloc-perturbing option.
+# This is cheap and useful for exposing code that depends on the fact that
+# malloc-related functions often return memory that is mostly zeroed.
+# If you have the time and cycles, use
Peter O'Gorman wrote:
On Sun, May 09, 2010 at 10:47:07PM +0200, Jim Meyering wrote:
+# Enable glibc's malloc-perturbing option.
+# This is cheap and useful for exposing code that depends on the fact that
+# malloc-related functions often return memory that is mostly zeroed.
+# If you have
Peter O'Gorman wrote:
On Sun, May 09, 2010 at 10:47:07PM +0200, Jim Meyering wrote:
+# Enable glibc's malloc-perturbing option.
+# This is cheap and useful for exposing code that depends on the fact that
+# malloc-related functions often return memory that is mostly zeroed.
+# If you have
