On Mon, Jul 31, 2017 at 11:54:12AM -0600, Jeff Law wrote:
> On 07/31/2017 11:23 AM, Segher Boessenkool wrote:
> > On Tue, Aug 01, 2017 at 01:12:41AM +0900, Oleg Endo wrote:
> >> I could probably write a similar rant. This is the life of a "minority
> >> target programmer". Most development effort
On 07/31/2017 11:23 AM, Segher Boessenkool wrote:
> On Tue, Aug 01, 2017 at 01:12:41AM +0900, Oleg Endo wrote:
>> I could probably write a similar rant. This is the life of a "minority
>> target programmer". Most development efforts are being done with
>> primary targets in mind. And as a result
On 07/31/2017 10:49 AM, Joel Sherrill wrote:
>
>
> On 7/31/2017 11:12 AM, Oleg Endo wrote:
>> On Mon, 2017-07-31 at 15:25 +0200, Georg-Johann Lay wrote:
>>> Around 2010, someone who used a code snipped that I published in
>>> a wiki, reported that the code didn't work and hang in an
>>> endless l
On Tue, Aug 01, 2017 at 01:12:41AM +0900, Oleg Endo wrote:
> I could probably write a similar rant. This is the life of a "minority
> target programmer". Most development efforts are being done with
> primary targets in mind. And as a result, most changes are being
> tested only on such targets.
On 31/07/17 17:12, Oleg Endo wrote:
> On Mon, 2017-07-31 at 15:25 +0200, Georg-Johann Lay wrote:
>> Around 2010, someone who used a code snipped that I published in
>> a wiki, reported that the code didn't work and hang in an
>> endless loop. Soon I found out that it was due to some GCC
>> problem
On Tue, 1 Aug 2017, Oleg Endo wrote:
> To improve the situation, we'd need a lot more target specific tests
> which test for those regressions that you have mentioned. Then of
> course somebody has to run all those tests on all those various
> targets. I think that's the biggest problem. But st
On 7/31/2017 11:12 AM, Oleg Endo wrote:
On Mon, 2017-07-31 at 15:25 +0200, Georg-Johann Lay wrote:
Around 2010, someone who used a code snipped that I published in
a wiki, reported that the code didn't work and hang in an
endless loop. Soon I found out that it was due to some GCC
problem, and
On Mon, 2017-07-31 at 15:25 +0200, Georg-Johann Lay wrote:
> Around 2010, someone who used a code snipped that I published in
> a wiki, reported that the code didn't work and hang in an
> endless loop. Soon I found out that it was due to some GCC
> problem, and I got interested in fixing the compi
Around 2010, someone who used a code snipped that I published in
a wiki, reported that the code didn't work and hang in an
endless loop. Soon I found out that it was due to some GCC
problem, and I got interested in fixing the compiler so that
it worked with my code.
1 1/2 years later, in 2011, I
