Bug#932989: gcc-avr: which upstream to track

2020-01-12 Thread Osamu Aoki
Hi, On Sun, Jan 12, 2020 at 08:36:49AM +0100, Hakan Ardo wrote: > Hi, > thanx a lot for the great summary of the situation! Historically, the > issue with "community" versions of the avr toolchain have been the > lack of support for all AVR devices. Especially newer once. I don't > know what the

Bug#932989: gcc-avr: which upstream to track

2020-01-11 Thread Hakan Ardo
Hi, thanx a lot for the great summary of the situation! Historically, the issue with "community" versions of the avr toolchain have been the lack of support for all AVR devices. Especially newer once. I don't know what the situation is there with the Arduino toolcahin. I agree that providing two

Bug#932989: gcc-avr: which upstream to track

2020-01-11 Thread Osamu Aoki
Hi again, I checked meaning of GCC versions. GCC development time lines: https://gcc.gnu.org/develop.html#timeline As for ISO C99 conformance: https://gcc.gnu.org/c99status.html The last mentioned version was GCC 5 for "extended identifiers". So GCC 5 as supported by the vendor

Bug#932989: gcc-avr: which upstream to track

2020-01-11 Thread Osamu Aoki
Hi (The URL for avr-gcc for Linux in my previous post was wrong but it isn't important ...) Arduino seems to built avr-gcc with https://github.com/arduino/toolchain-avr It's opening page states: binutils-2.26 gcc-5.4.0 avr-libc-2.0.0 gdb-7.8 Not gcc-7.3.0 as released as

Bug#932989: gcc-avr: which upstream to track

2020-01-11 Thread Osamu Aoki
Hi, This is a review of CC/C++ for AVR. Debian Buster: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture