Re: Workaround for bugs 42614 and 42691 in GCC 4.4.2

2018-08-16 Thread Vicent Brocal Tortosa
Hello Jeff, > El 16 ag 2018, a les 17:50, Jeff Law va escriure: > > On 08/16/2018 09:43 AM, Vicent Brocal Tortosa wrote: >> Hello, >> >> We are forced to use version 4.4.2 of GCC C compiler for a certain project >> and to analyze the potential impact, to o

Workaround for bugs 42614 and 42691 in GCC 4.4.2

2018-08-16 Thread Vicent Brocal Tortosa
Hello, We are forced to use version 4.4.2 of GCC C compiler for a certain project and to analyze the potential impact, to our software, of bugs detected for this GCC version. I am already aware that bugs reported for 4.4.x versions may also be present in 4.4.2, but for the moment we have decid

Re: Impact of bugs on different versions.

2017-09-21 Thread Vicent Brocal Tortosa
El 21 set 2017, a les 17:50, Martin Sebor va escriure: > > On 09/21/2017 06:22 AM, Vicent Brocal wrote: >> For a C standalone application (no libs) I selected the following >> components: c, inline-asm, ipa, preprocessor, regression, >> rtl-optimization, target, tree-o

Re: Impact of bugs on different versions.

2017-09-21 Thread Vicent Brocal
to find some way to trim it down. Thanks anyway for the indications. On 21/09/17 14:02, Jonathan Wakely wrote: > On 21 September 2017 at 12:56, Vicent Brocal wrote: >> Hello everyone, >> >> I am trying to figure out which are the problems affecting a specific >> v

Impact of bugs on different versions.

2017-09-21 Thread Vicent Brocal
Hello everyone, I am trying to figure out which are the problems affecting a specific version of GCC (4.4.2) from the information in the bug tracker (https://gcc.gnu.org/bugzilla/). So far I have been able to get a list of the bugs restricted to standalone C components (c, inline-asm, ipa, prepro