Compiler bug reports and ways of getting fixes?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Compiler bug reports and ways of getting fixes?

John Dallman
I seem to have found a optimizer bug in clang version 9.0.8 from NDK21b. I'm compiling C code for AArch64. I can get round it with reduced optimization on one file for now, but I'd like to get a fix if possible. 

Where should I submit a bug report? 

The code I'm working with is closed-source and commercially confidential. Will the bug report be publicly accessible? I can cope with that, I just have to do more work genericising the code. 

Is there a way of getting a fix for NDK21b, or will I have to move to a later NDK? That attraction of staying with 21b is that it's an LTS version; I work with multiple platforms and it's very advantageous to use LTS versions. 

Thanks,

John Dallman

--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/CAH1xqg%3DZkY3VeMAg4zt_wTwjHTprfJi8G92dNrUTG3n4WwpLYw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Compiler bug reports and ways of getting fixes?

Dan Albert
Go ahead and submit the bug to the NDK: https://github.com/android/ndk/issues/new/choose. Even if an upstream bug is eventually needed, we'll want to track it there anyway.

The code I'm working with is closed-source and commercially confidential. Will the bug report be publicly accessible? I can cope with that, I just have to do more work genericising the code.

Something publicly accessible is easier to work with just in case we need to get more eyes on it, but if sharing it privately is an option we can make that work too. If you want to go that route, go ahead and file an NDK bug without a repro case explaining that and we'll figure out how to get it to the right person from there. 

Is there a way of getting a fix for NDK21b, or will I have to move to a later NDK? That attraction of staying with 21b is that it's an LTS version; I work with multiple platforms and it's very advantageous to use LTS versions. 

r21 yes, but r21b refers to exactly one build :) If it's a regression from r20 then we'll probably release a fix to r21 for it (it depends on the scope of the fix). 

On Thu, Jun 4, 2020 at 9:58 AM John Dallman <[hidden email]> wrote:
I seem to have found a optimizer bug in clang version 9.0.8 from NDK21b. I'm compiling C code for AArch64. I can get round it with reduced optimization on one file for now, but I'd like to get a fix if possible. 

Where should I submit a bug report? 

The code I'm working with is closed-source and commercially confidential. Will the bug report be publicly accessible? I can cope with that, I just have to do more work genericising the code. 

Is there a way of getting a fix for NDK21b, or will I have to move to a later NDK? That attraction of staying with 21b is that it's an LTS version; I work with multiple platforms and it's very advantageous to use LTS versions. 

Thanks,

John Dallman

--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/CAH1xqg%3DZkY3VeMAg4zt_wTwjHTprfJi8G92dNrUTG3n4WwpLYw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/CAFVaGhuft1g%3Deh9d6fHQMd1RNvmrAzv9Q9qFzR75MZHrdguMVQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Compiler bug reports and ways of getting fixes?

John Dallman
> Go ahead and submit the bug to the NDK: https://github.com/android/ndk/issues/new/choose.  

Will do. I'll see if I can get it to public acceptability, but I won't break my heart trying. 

> r21 yes, but r21b refers to exactly one build :) 

Got it! 

> If it's a regression from r20 then we'll probably release a fix to r21 for it (it depends on the scope of the fix).   

It's a regression from r16. I understand about scope of fixes in compilers, having done this before. 

Thanks,

John



On Thu, Jun 4, 2020 at 7:02 PM 'Dan Albert' via android-ndk <[hidden email]> wrote:
Go ahead and submit the bug to the NDK: https://github.com/android/ndk/issues/new/choose. Even if an upstream bug is eventually needed, we'll want to track it there anyway.

The code I'm working with is closed-source and commercially confidential. Will the bug report be publicly accessible? I can cope with that, I just have to do more work genericising the code.

Something publicly accessible is easier to work with just in case we need to get more eyes on it, but if sharing it privately is an option we can make that work too. If you want to go that route, go ahead and file an NDK bug without a repro case explaining that and we'll figure out how to get it to the right person from there. 

Is there a way of getting a fix for NDK21b, or will I have to move to a later NDK? That attraction of staying with 21b is that it's an LTS version; I work with multiple platforms and it's very advantageous to use LTS versions. 

r21 yes, but r21b refers to exactly one build :) If it's a regression from r20 then we'll probably release a fix to r21 for it (it depends on the scope of the fix). 

On Thu, Jun 4, 2020 at 9:58 AM John Dallman <[hidden email]> wrote:
I seem to have found a optimizer bug in clang version 9.0.8 from NDK21b. I'm compiling C code for AArch64. I can get round it with reduced optimization on one file for now, but I'd like to get a fix if possible. 

Where should I submit a bug report? 

The code I'm working with is closed-source and commercially confidential. Will the bug report be publicly accessible? I can cope with that, I just have to do more work genericising the code. 

Is there a way of getting a fix for NDK21b, or will I have to move to a later NDK? That attraction of staying with 21b is that it's an LTS version; I work with multiple platforms and it's very advantageous to use LTS versions. 

Thanks,

John Dallman

--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/CAH1xqg%3DZkY3VeMAg4zt_wTwjHTprfJi8G92dNrUTG3n4WwpLYw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/CAFVaGhuft1g%3Deh9d6fHQMd1RNvmrAzv9Q9qFzR75MZHrdguMVQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/CAH1xqgkYFba3bAw4uB8s-mDoHA_YWzkNGQamD4x0Pd12x4B9RA%40mail.gmail.com.