WinAVR vs Atmel Studio toolchains

Go To Last Post
14 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What's the specific differences between the WinAVR toolchain and Atmel's Studio 6 toolchain ?

PLEASE: Reply only if you know specifics.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

WinAVR: avr-gcc = 4.3.3, AVR-LibC = 1.6.7, binutils = 2.19
As6 Toolchain: avr-gcc= 4.6.2, AVR-LibC = 1.8.0, binutils = 2.22

There are probably a thousand or more differences listed in the development history between 4.3.3 and 4.6.2 I presume you don't intend someone to list them all?

Also note that these packages are "distributions". They are not just a compiler but also include (different versions) of binutils and AVR-LibC so one would need to explore the Bugzilla's for those too to understand the many differences there.

Until AS6 appeared the general advice here would have been stick with WinAVR unless you need device support for a recent device only covered in Toolchain. But then Atmel got their act together and the "toolchain" in AS6 isn't half bad. So it's 50:50 as to which one to choose if the device is supported but it's unquestionable that "Toolchain" has support for more devices as it benefited from 2 more years of development.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Where can I find the specific compiler differences excluding device support ?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

release notes?

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The GCC release history is here: http://gcc.gnu.org/releases.html

You can drill down into each release to see what changes where made, and what bug (Problem Reports, or "PR"s where fixed). For example, the fixes done for 4.6.1 is here: http://gcc.gnu.org/bugzilla/bugl... .

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm asking for the differences between WinAVR and Visual Studio 6 versions of the gcc/g++ compiler, NOT the differences between versions of the same package from either of the 2 suppliers. Atmel has, apparently, modified the open-source code.

Please: Reply only if you know specifics.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Atmel has, apparently, modified the open-source code.
Look at the patches then. They describe the differences from gcc exactly.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AFAIK WinAVR is based on GCC 4.3.3 and the AVR Toolchain (that comes with AVR Studio) is 4.6.2. No-one knows the specific differences from memory. There are likely thousands of changes made between 4.3.3 and 4.6.2. Anyone wanting to list the differences would need to browse the change history. I pointed to where (at least parts of) that history is documented. I was actually trying to help you get to some specifics.

It is obvious that you do not want such help, so I will most happily leave this thread here and now.

A last comment: If Atmel has introduced patches developed in-house, then they have either pushed them "upwards" (and then you should be able to locate them) or they are (at least for the time being) kept inside Atmel. Regardless of if this is compatible with the GCC license I do not think that Atmel will publish them here and now as an answer to your question.

Bye.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

A last comment: If Atmel has introduced patches developed in-house, then they have either pushed them "upwards" (and then you should be able to locate them) or they are (at least for the time being) kept inside Atmel. Regardless of if this is compatible with the GCC license I do not think that Atmel will publish them here and now as an answer to your question.

I'm told we're working on getting them upstream, but the patches are released in source form with the Atmel Toolchain download packages.

pascor: People gave you all the information one could reasonably expect given your question. Asking for information and just replying with "but I want specifics" over and over again won't help, you need to tell us exactly what you want to know.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Pascor,

I take it you are aware of:

http://gcc.gnu.org/bugzilla/bugl...

Or were you looking for someone to read it all out to you? Jeesh!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Clawson: I had no idea that there were so many unresolved bugs in the gnu gcc version. Sounds like it's just not "ready for prime time". That there's a glaring bug with the PROGMEM definition in the current 4.3.3 version and they are going to wait until they release version 4.6 to fix it seems to underscore the situation.

I'll have to compare the results of the 2 toolchains as I go along to see what are the differences.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

in the current 4.3.3 version

What on earth are you talking about? The "current" version of GCC is 4.8.x. Version 4.3 was several years ago.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The current release series (bug fixes only) of GCC is 4.7
The oldes maintained release series (bug fixes only) of GCC is 4.6
The active development (new features, not yet released) is future 4.8.

If anybody feels that the GCC development proceeds too slow, he/she can contribute to the project in order so speed it up. Thanks.

If you are not satisfied with the packages you find on the web or from some destributor, please feel free to build whatever compiler version with whatever patches, fixes, extensions or changes you deem appropriate.

avrfreaks does not support Opera. Profile inactive.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

and they are going to wait until they release version 4.6 to fix it

Who are "they" that you talk about?

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]