I want to add a test case to the gfortran testsuite for PR 65563.
If all goes right, running the test case will
a) terminate the program with an error message (to be checked for)
b) create a file, which needs to be cleaned up after the test case
is run.
a) is clear, but how do I do b)? I hav
On Sun, Mar 29, 2015 at 2:28 PM, Thomas Koenig wrote:
> I want to add a test case to the gfortran testsuite for PR 65563.
> If all goes right, running the test case will
>
> a) terminate the program with an error message (to be checked for)
>
> b) create a file, which needs to be cleaned up after
Hi Janne,
> ! { dg-final { remote_file build delete "pr64770test.dat" } }
did the trick. It is not mentioned in the docs, though.
Thanks!
Thomas
On 03/29/2015 04:50 AM, Janne Blomqvist wrote:
On Sun, Mar 29, 2015 at 2:28 PM, Thomas Koenig wrote:
I want to add a test case to the gfortran testsuite for PR 65563.
If all goes right, running the test case will
a) terminate the program with an error message (to be checked for)
b) create a f
Hello everyone,
Consider the following program.
#include
#include
struct foo1 { char s[80]; };
struct foo2 { char s[80]; } __attribute__ ((aligned (64)));
struct bar1 { struct foo1 f; int i; };
struct bar2 { struct foo2 f; int i; };
#define P(arg) printf("sizeof(" #arg ") = %u\n", (unsigned)si
Mason writes:
> Hello everyone,
>
> Consider the following program.
This mailing list is about the development of gcc, for user questions
please use gcc-h...@gcc.gnu.org instead.
> gcc lays out bar2 like this:
> foo2(80) padding(48) i(4) padding(60)
struct foo2 has size 128, not 80. The paddi
On 29/03/2015 17:35, Andreas Schwab wrote:
> Mason wrote:
>
>> Consider the following program. [snip]
>
> This mailing list is about the development of gcc, for user questions
> please use gcc-h...@gcc.gnu.org instead.
Thanks, I will re-send my original message to gcc-help.
Please be aware tha
Hi,
why does gcc (4.4.7 and 4.8.2) sometimes warn and sometimes not warn
when undefined behavior is invoked when making illegal function
pointer conversions?
For instance, consider the code below:
-
/* Tested with gcc 4.4.7 and 4.8.2 */
#include
#include
bool boolFunctionThatReturnsFa
Godmar Back writes:
> ps: I would like to see the warning, of course, since casting a bool
> returning function to an int returning function is undefined behavior.
The cast itself is ok, the undefined behavior only occurs when calling
it without casting back.
Andreas.
--
Andreas Schwab, sch..
On Sun, Mar 29, 2015 at 3:26 PM, Andreas Schwab wrote:
> Godmar Back writes:
>
>> ps: I would like to see the warning, of course, since casting a bool
>> returning function to an int returning function is undefined behavior.
>
> The cast itself is ok, the undefined behavior only occurs when calli
On 29 March 2015 at 19:32, Godmar Back wrote:
> Why does assigning boolFunctionThatReturnsFalse to a variable f after
> the cast, instead of directly dereferencing it, silence the compiler's
> warnings?
Because the cast itself is OK, and the call that results in undefined
behaviour is separate fro
Snapshot gcc-5-20150329 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20150329/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
12 matches
Mail list logo
