: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
Target Milestone: ---
GCC-6.1.0
x86_64-pc-linux-gnu and x86_64-apple-darwin15.4.0
Running the following test:
make -s -C gcc check-gcc RUNTESTFLAGS
: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
Created attachment 33214
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33214&action=edit
test log
x86_64-unknown-linux-gnu
GCC version
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61965
--- Comment #1 from Sabrina Souto ---
It happened again, now for this test: ../gcc/testsuite/gcc.dg/pr39794.c
Hera is the line executed:
/home/sabrina/gcc/objdir/gcc/xgcc -B/home/sabrina/gcc/objdir/gcc/
/home/sabrina/gcc/gcc-4.8.2/gcc/testsuite/
: critical
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
GCC-4.9.1
x86_64-apple-darwin11.4.2
Running the following tests:
1)
make -s -C gcc check-gcc RUNTESTFLAGS="dg.exp=pr39794.c
--target_board
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61980
--- Comment #2 from Sabrina Souto ---
Thank you for the confirmation Richard.
Just a suggestion: if the option -fcheck-data-deps does not work well, maybe
this option should be removed from the code or at least have a comment in the
documentatio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61980
--- Comment #4 from Sabrina Souto ---
I don't have much experience with GCC, so I'm a bit confused with your 2
answers, please help me understanding what is happening: Based both on the
documentation and the results, I understood that the result
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61980
--- Comment #6 from Sabrina Souto ---
OK, Thank you.
(In reply to Richard Biener from comment #5)
> (In reply to Sabrina Souto from comment #4)
> > I don't have much experience with GCC, so I'm a bit confused with your 2
> > answers, please help
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
GCC-4.10.0 (trunk)
x86_64-apple-darwin11.4.2
Running the following test:
make -s -C gcc check-gcc RUNTESTFLAGS="dg.exp=20090922-1.c
--target_board=unix/-fcheck-data-deps"
GCC th
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
GCC-4.10.0 (trunk)
x86_64-apple-darwin11.4.2
Running the following test:
make -s -C gcc check-gcc RUNTESTFLAGS="dg.exp=pr47684.c
--target_board=unix/-O3/-fno-tree-vectorize"
GCC th
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
GCC-4.10.0 (trunk)
x86_64-apple-darwin11.4.2
Running the following test:
make -s -C gcc check-gcc RUNTESTFLAGS="dg-torture.exp=pr44
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
GCC-4.10.0 (trunk)
x86_64-apple-darwin11.4.2
Running the following test:
make -s -C gcc check-gcc RUNTESTFLAGS="dg-torture.exp=pr53703.c
--target_board=unix/-fsanitize=address"
GC
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
GCC-4.10.0 (trunk)
x86_64-apple-darwin11.4.2
Running the following test:
make -s -C gcc check-gcc
RUNTESTFLAGS="dg-torture.exp=Wsizeof-pointer-memaccess1.c
--target_board=unix/-fsanitize=address&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62141
--- Comment #1 from Sabrina Souto ---
Created attachment 33326
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33326&action=edit
Log of the test execution
iority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
GCC-4.10.0 (trunk)
x86_64-apple-darwin11.4.2
Running the following test:
make -s -C gcc check-gcc RUNTESTFLAGS="dg.exp=pr55027.c
--target_board=unix/-O0"
GCC p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62158
--- Comment #2 from Sabrina Souto ---
Created attachment 33350
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33350&action=edit
Execution log
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62158
--- Comment #3 from Sabrina Souto ---
You are right, but indeed this test ran with the option -Ofast, I did not
explicitly use this option in the command line because this is already done by
DejaGnu, as you can see in the test code below.
Test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62140
--- Comment #6 from Sabrina Souto ---
I checked with the current code in trunk and the test is passing, did you fixed
it?
What do you mean by "close"? Change the status for "RESOLVED"?
(In reply to Yury Gribov from comment #5)
> Sabrina, could
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71512
--- Comment #3 from Sabrina Souto ---
I had a similar result, but different failure, for another test+configuration
(see below). I would like to know if it is another (different) bug.
GCC-6.1.0
x86_64-pc-linux-gnu and x86_64-apple-darwin15.4.0
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
Target Milestone: ---
GCC-6.1.0
x86_64-pc-linux-gnu and x86_64-apple-darwin15.4.0
Running the following test:
make -s -C gcc check-gcc RUNTESTFLAGS="dg-torture.exp=pr48
Assignee: unassigned at gcc dot gnu.org
Reporter: sabrinadfs at gmail dot com
Target Milestone: ---
GCC-6.1.0
x86_64-pc-linux-gnu and x86_64-apple-darwin15.4.0
When I run the following test with -fno-ivopts option:
make -s -C gcc check-gcc RUNTESTFLAGS="tree-ssa.exp=loop
20 matches
Mail list logo