public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/59732] New: [4.9 Regression] ICE with -fopenmp: invalid address operand in MEM_REF
@ 2014-01-08 23:01 burnus at gcc dot gnu.org
2014-01-09 9:45 ` [Bug middle-end/59732] " rguenth at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2014-01-08 23:01 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59732
Bug ID: 59732
Summary: [4.9 Regression] ICE with -fopenmp: invalid address
operand in MEM_REF
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code, openmp
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Created attachment 31780
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31780&action=edit
Test case, compile with "g++ -fopenmp"
Found when compiling Open MPI (trunk version) in the Vampire Trace (vt)
component.
I marked it as regression as I do not see it with GCC 4.8, however, my GCC 4.8
is compiled without checking.
Compiling ompi/contrib/vt/vt/tools/vtfilter/vt_filter_trc.cc - or the attached
test case - fails as follows:
$ g++ -S -fopenmp test46.ii
test46.ii: In member function 'bool
FilterTraceC::processEventsAndStatistics()':
test46.ii:61:54: error: invalid address operand in MEM_REF
const set<uint32_t>& procs = m_streamProcs[stream];
^
MEM[(struct FilterTraceC *)<<< error >>>];
D.2586 = &MEM[(struct FilterTraceC *)<<< error >>>].m_streamProcs;
test46.ii:61:54: internal compiler error: verify_gimple failed
0xbd7da6 verify_gimple_in_cfg(function*)
../../gcc/tree-cfg.c:4854
0xaffcc7 execute_function_todo
../../gcc/passes.c:1854
0xb005b3 execute_todo
../../gcc/passes.c:1884
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/59732] [4.9 Regression] ICE with -fopenmp: invalid address operand in MEM_REF
2014-01-08 23:01 [Bug middle-end/59732] New: [4.9 Regression] ICE with -fopenmp: invalid address operand in MEM_REF burnus at gcc dot gnu.org
@ 2014-01-09 9:45 ` rguenth at gcc dot gnu.org
2014-01-09 15:07 ` mpolacek at gcc dot gnu.org
2014-01-09 20:09 ` burnus at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: rguenth at gcc dot gnu.org @ 2014-01-09 9:45 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59732
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.9.0
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/59732] [4.9 Regression] ICE with -fopenmp: invalid address operand in MEM_REF
2014-01-08 23:01 [Bug middle-end/59732] New: [4.9 Regression] ICE with -fopenmp: invalid address operand in MEM_REF burnus at gcc dot gnu.org
2014-01-09 9:45 ` [Bug middle-end/59732] " rguenth at gcc dot gnu.org
@ 2014-01-09 15:07 ` mpolacek at gcc dot gnu.org
2014-01-09 20:09 ` burnus at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2014-01-09 15:07 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59732
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I can't reproduce it with xg++ (GCC) 4.9.0 20140109 (experimental) configured
with --enable-checking=yes,rtl.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/59732] [4.9 Regression] ICE with -fopenmp: invalid address operand in MEM_REF
2014-01-08 23:01 [Bug middle-end/59732] New: [4.9 Regression] ICE with -fopenmp: invalid address operand in MEM_REF burnus at gcc dot gnu.org
2014-01-09 9:45 ` [Bug middle-end/59732] " rguenth at gcc dot gnu.org
2014-01-09 15:07 ` mpolacek at gcc dot gnu.org
@ 2014-01-09 20:09 ` burnus at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2014-01-09 20:09 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59732
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #1)
> I can't reproduce it with xg++ (GCC) 4.9.0 20140109 (experimental)
> configured with --enable-checking=yes,rtl.
I cannot reproduce it anymore either; I think I had some patch applied in that
build. Sorry for the wrong alert - and thanks for testing!
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-01-09 20:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-08 23:01 [Bug middle-end/59732] New: [4.9 Regression] ICE with -fopenmp: invalid address operand in MEM_REF burnus at gcc dot gnu.org
2014-01-09 9:45 ` [Bug middle-end/59732] " rguenth at gcc dot gnu.org
2014-01-09 15:07 ` mpolacek at gcc dot gnu.org
2014-01-09 20:09 ` burnus at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).