All,

This is from an email trail on gcc-patches. I was attempting to clean
up differences in the test suite between -fPIC and no -fPIC tests.

        * gcc.dg/assign-warn-3.c: Ditto.


Why in the world do you imagine this should depend on -fpic?

Here's the case that passes (no -fPIC):
Executing on host: /u2/gcc/head/osr5/gcc/xgcc -B/u2/gcc/head/osr5/gcc/ /u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c -O3 -std=c99 -pedantic-errors -fno-show-column -S -o assign-warn-3.s (timeout = 300)
/u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c: In function 'g1':
/u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c:13: warning: pointer targets in passing argument 1 of 'f1' differ in signedness
/u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c: In function 'g0':
/u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c:9: warning: pointer targets in passing argument 1 of 'f0' differ in signedness
output is:
/u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c: In function 'g1':
/u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c:13: warning: pointer targets in passing argument 1 of 'f1' differ in signedness
/u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c: In function 'g0':
/u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c:9: warning: pointer targets in passing argument 1 of 'f0' differ in signedness

PASS: gcc.dg/assign-warn-3.c  (test for warnings, line 9)
PASS: gcc.dg/assign-warn-3.c  (test for warnings, line 13)
PASS: gcc.dg/assign-warn-3.c (test for excess errors)

And here is the case that fails (-fPIC). I have no idea why those
warnings are not being ejected when compiling with -fPIC. Perhaps I
discovered a bug here by accident? I guess I should have looked at the
test case more carefully instead of just trying to silence the failure.

Executing on host: /u2/gcc/head/osr5/gcc/xgcc -B/u2/gcc/head/osr5/gcc/ /u2/gcc/head/gcc/gcc/testsuite/gcc.dg/assign-warn-3.c -O3 -std=c99 -pedantic-errors -fno-show-column -S -fPIC -o assign-warn-3.s (timeout = 300)
FAIL: gcc.dg/assign-warn-3.c  (test for warnings, line 9)
FAIL: gcc.dg/assign-warn-3.c  (test for warnings, line 13)
PASS: gcc.dg/assign-warn-3.c (test for excess errors)

Is this indeed a bug?

Kean

Reply via email to