| Author |
Message |
|
|
 Posted: May 03, 2012 - 08:44 AM |
|
Joined: Dec 20, 2002
Posts: 7276
Location: Dresden, Germany
|
|
> The OP's problem is in my opinion stack-overwrite related, far more
> probable than triggering an obscure compiler bug.
I disagree. As Johann already suspected, it's very likely bug #46779.
It is really "unstable" in that changing just a couple of lines in the
sourcecode might decide between working and broken code. Been there
myself. |
_________________
Jörg Wunsch
Please don't send me PMs, use email if you want to approach me personally.
Please read the `General information...' article before.
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 08:52 AM |
|
Joined: Dec 16, 2005
Posts: 3086
Location: Bratislava, Slovakia
|
|
Fancy a bet, Jörg? 
Jan |
|
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 08:59 AM |
|
Joined: Mar 27, 2002
Posts: 18528
Location: Lund, Sweden
|
|
|
Quote:
I want it to improve just as much as everyone else, but it won't unless the Atmel team are aware of all the issues.
Works both ways, Dean. People will be more inclined to contribute if they know they are reporting something new, rather than something known. As our resident mole - go over to the tools folks and tell them to have a published version of their bug tracker list.
-----
As for building the avr-gcc tool chain, I've been contemplating it. The instructions in the avrlibc documentation seems to be good, but it is when I look into the totally mysterious world that is "patches, how and which to apply, etc...", that I give up before really having started. |
|
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 10:42 AM |
|
Joined: Dec 20, 2002
Posts: 7276
Location: Dresden, Germany
|
|
> patches, how and which to apply
Start building without patches. If all works out, you can see what you
really need.
At the rate Johann has been integrating bugfixes, and even the Xmega patch
series lately, I think you'll be fine with an unpatched GCC version now in
most situations (i.e. for everything except really new AVR devices which
did not make their way back upstream). |
_________________
Jörg Wunsch
Please don't send me PMs, use email if you want to approach me personally.
Please read the `General information...' article before.
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 11:32 AM |
|
Joined: Jan 23, 2004
Posts: 9820
Location: Trondheim, Norway
|
|
|
Quote:
Works both ways, Dean. People will be more inclined to contribute if they know they are reporting something new, rather than something known. As our resident mole - go over to the tools folks and tell them to have a published version of their bug tracker list.
I know, I think it's silly too - but the tools team is worried about exposing sensitive internal information (which can happen, since it's internal people throw around internal documents all the time). Our Apps department is a little different since we are open source anyway.
For now, I'm going to have to act as a human JIRA bot, shuffling reports in an out of the system (censoring as required).
- Dean  |
_________________
Atmel Studio 6.1 is now released, grab it here.
Report AS6/ASF bugs here.
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 11:44 AM |
|
Joined: Mar 27, 2002
Posts: 18528
Location: Lund, Sweden
|
|
Thanks, Dean!
[Please ignorethe rest, this is just a rant]
Quote:
Our Apps department is a little different since we are open source anyway.
Last time I checked GCC and Binutils was GPL or whatever. Are the lawyers, the web designer and the tools team sharing a floor and a coffee room?  |
|
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 11:52 AM |
|
Joined: Jan 23, 2004
Posts: 9820
Location: Trondheim, Norway
|
|
|
Quote:
Last time I checked GCC and Binutils was GPL or whatever. Are the lawyers, the web designer and the tools team sharing a floor and a coffee room? Evil or Very Mad
I don't know much about it, but it appears the patches for the Atmel Toolchain are located in the "source" folder - in both the standalone and Atmel Studio releases of the toolchain.
- Dean |
_________________
Atmel Studio 6.1 is now released, grab it here.
Report AS6/ASF bugs here.
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 12:00 PM |
|
Joined: Jul 18, 2005
Posts: 62228
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
Quote:
I don't know much about it, but it appears the patches for the Atmel Toolchain are located in the "source" folder - in both the standalone and Atmel Studio releases of the toolchain.
Except that if you are a Linux user those files are embedded inside an installation .exe that requires Windows to run
(OK I know they are published separately on the web but that is not properly version managed - you cannot tell which variant of 5.1 any set applies to fo example). |
_________________
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 12:19 PM |
|
Joined: Feb 12, 2005
Posts: 16269
Location: Wormshill, England
|
|
Surely you could have a simple list of reported bugs.
As far as I can see, the Bugzilla has no evidence of the incorrectly spelled interrupt vectors in the avr-gcc <iomxxxA.h> header files.
In fact it does not even seem to have anything much with avr-gcc Toolchain.
David. |
|
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 01:22 PM |
|
Joined: Dec 21, 2006
Posts: 1483
Location: Saar-Lor-Lux
|
|
|
abcminiuser wrote:
Quote:
Works both ways, Dean. People will be more inclined to contribute if they know they are reporting something new, rather than something known. As our resident mole - go over to the tools folks and tell them to have a published version of their bug tracker list.
I know, I think it's silly too - but the tools team is worried about exposing sensitive internal information (which can happen, since it's internal people throw around internal documents all the time).
They use a bugtracker like bugzilla to throw around internal documents all the time?
There is no document management system? Or email? Or sharing files?
And there would be no different between an internel lissue tracker and an official one outside the firewall?
Well, ... |
|
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 01:33 PM |
|
Joined: Dec 16, 2005
Posts: 3086
Location: Bratislava, Slovakia
|
|
|
SprinterSB wrote:
abcminiuser wrote:
Quote:
Works both ways, Dean. People will be more inclined to contribute if they know they are reporting something new, rather than something known. As our resident mole - go over to the tools folks and tell them to have a published version of their bug tracker list.
I know, I think it's silly too - but the tools team is worried about exposing sensitive internal information (which can happen, since it's internal people throw around internal documents all the time).
They use a bugtracker like bugzilla to throw around internal documents all the time?
There is no document management system? Or email? Or sharing files?
And there would be no different between an internel lissue tracker and an official one outside the firewall?
Well, ...
I believe the problem is not that whole internal document may get public inadvertently, rather, that snippets of potentially sensitive (and sometimes even more so without proper context) internal information may be leaked by the insider writing to a public place by mistake.
Not that I like the status quo, just understand why the resistance...
JW
PS. Moderator, now this thread got so HOPELESSLY OT, deserving to be cut to quite a couple of pieces... |
|
|
| |
|
|
|
|
|
|
Posted: May 03, 2012 - 06:28 PM |
|
Joined: Dec 06, 2007
Posts: 2512
Location: Redmond, WA USA
|
|
|
wek wrote:
PS. Moderator, now this thread got so HOPELESSLY OT, deserving to be cut to quite a couple of pieces...
I couldn't agree more.
I would like to continue to have a discussion about building an avr-gcc for windows, but I feel this is not the place for it. |
_________________
Larry
Those afraid to embrace the future will quickly fade into the past. - larryvc
|
| |
|
|
|
|
|
FAQ
Search
Register
Log in to check your private messages
Log in
Maximize
RSS
