Re: [go-nuts] Strange behaviour with loops #45192, #45175

[Sebastien Rosset]

That's a great idea. Thank you! I am doing that right now.

On Wed, Apr 7, 2021 at 5:05 PM 'Keith Randall' via golang-nuts <
golang-nuts@googlegroups.com> wrote:

> If you look at CL 304251, there's one place where we added "return false".
> Put a panic just before that line (in 1.15.11 or 1.16.3), rebuild the
> compiler, then rebuild your program and see if your program triggers that
> panic.
>
>
> On Wednesday, April 7, 2021 at 2:37:53 PM UTC-7 Ian Lance Taylor wrote:
>
>> On Wed, Apr 7, 2021 at 1:47 PM sro...@gmail.com 
>> wrote:
>> >
>> > Is there a way to analyze a go program and determine whether it is
>> susceptible to bug https://github.com/golang/go/issues/45175?
>> > While the obvious solution is to upgrade to 1.15.11 or 1.16.3, it would
>> still be useful to analyze existing programs, either as a compiled binary
>> or source code.
>>
>> There is no simple way to do this. It's an unfortunate bug, but it's
>> rare, and is dependent on the exact compilation process.
>>
>> The simplest way to detect a possible problem might be to compile the
>> package with both 1.15.10 and 1.15.11 and compare the generated
>> output.
>>
>> Ian
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "golang-nuts" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/golang-nuts/28J9lE4yoHI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/f3b69bbf-3a13-4786-924c-0e874c49ffd9n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAJsvqr1cc1ye6V%3DXLPi9qjWe5aa5%3DRkW0pLRM6vTsn-W_5u83Q%40mail.gmail.com.

Re: [go-nuts] Strange behaviour with loops #45192, #45175

['Keith Randall' via golang-nuts]

If you look at CL 304251, there's one place where we added "return false". 
Put a panic just before that line (in 1.15.11 or 1.16.3), rebuild the 
compiler, then rebuild your program and see if your program triggers that 
panic.


On Wednesday, April 7, 2021 at 2:37:53 PM UTC-7 Ian Lance Taylor wrote:

> On Wed, Apr 7, 2021 at 1:47 PM sro...@gmail.com  wrote:
> >
> > Is there a way to analyze a go program and determine whether it is 
> susceptible to bug https://github.com/golang/go/issues/45175?
> > While the obvious solution is to upgrade to 1.15.11 or 1.16.3, it would 
> still be useful to analyze existing programs, either as a compiled binary 
> or source code.
>
> There is no simple way to do this. It's an unfortunate bug, but it's
> rare, and is dependent on the exact compilation process.
>
> The simplest way to detect a possible problem might be to compile the
> package with both 1.15.10 and 1.15.11 and compare the generated
> output.
>
> Ian
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/f3b69bbf-3a13-4786-924c-0e874c49ffd9n%40googlegroups.com.

Re: [go-nuts] Strange behaviour with loops #45192, #45175

[Ian Lance Taylor]

On Wed, Apr 7, 2021 at 1:47 PM sro...@gmail.com  wrote:
>
> Is there a way to analyze a go program and determine whether it is 
> susceptible to bug https://github.com/golang/go/issues/45175?
> While the obvious solution is to upgrade to 1.15.11 or 1.16.3, it would still 
> be useful to analyze existing programs, either as a compiled binary or source 
> code.

There is no simple way to do this.  It's an unfortunate bug, but it's
rare, and is dependent on the exact compilation process.

The simplest way to detect a possible problem might be to compile the
package with both 1.15.10 and 1.15.11 and compare the generated
output.

Ian

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAOyqgcX2n%2BeGy8RG9-9jG%2BeOo8%2B8hRqT1R2Qg9TVM01iwOqzhQ%40mail.gmail.com.

[go-nuts] Strange behaviour with loops #45192, #45175

[sro...@gmail.com]

Is there a way to analyze a go program and determine whether it is 
susceptible to bug https://github.com/golang/go/issues/45175?
While the obvious solution is to upgrade to 1.15.11 or 1.16.3, it would 
still be useful to analyze existing programs, either as a compiled binary 
or source code.
Thank you. Sebastien

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/2818753d-406e-4a46-bc32-d52338614140n%40googlegroups.com.