Hello, Like clearly said in my previous mail, it is the "data-flow-types / dataflow+" optimization step that fails. -O2 is not working -O2 -fno-datatype is working.
But 1) I do not like to add specific compilation options for a certain module because of a bug. 2) If it arrive here it can arrive elsewhere so I prefer to fix bigloo... Yes it is working in released 4.3a (with -O6) . And not working in the current 4.3b from -O2. Thanks Pierre-Francois -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sven Hartrumpf Sent: Monday, March 12, 2018 12:37 PM To: [email protected] Subject: Re: [bigloo] Dataflow+ debuging Hello. Pierre-Francois wrote, 2018-03-09: > I have an issue when compiling: The Dataflow+ fail and "remove" a part of the > code: > Unfortunatly I did not success to make a testcase.... Issue is probably > coming by the fact that several things are coming and used in several modules. > For information, it is working in 4.3a. Is it working in the released version 4.3a? In which versions do you get the problematic binary? If you suspect a too aggressive optimization, it is advisable to determine the optimization option(s) that turn from good to bad. You have not specified your bigloo compiler options, but in general you could try with: -O3 -O4 -O5 and proceed until your binary is incorrect. If you have identified the problematic step (e.g. from -O4 to -O5), you can add the -O5-specific options one by one to -O4. Greetings Sven
