AVR C Runtime Library - Bugs: bug #28837, using PSTR with c++ produces...
You are not allowed to post comments on this tracker with your current authentication level.
bug #28837: using PSTR with c++ produces warnings
Submitter: | Hose Bag <user> | ||
Submitted: | Sun 07 Feb 2010 11:01:18 PM UTC | ||
Category: | Header | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | None |
Status: | Invalid | Assigned to: | joerg_wunsch |
Percent Complete: | 0% | Open/Closed: | Closed |
Release: | 1.6.2 | Fixed Release: | None |
Jump to the original submission
Sat 29 Oct 2011 01:04:02 PM UTC, comment #7: |
Volker Kuhlmann <vok> |
Sat 29 Oct 2011 11:44:38 AM UTC, comment #6:
|
Georg-Johann Lay <gjlayde> |
Sat 29 Oct 2011 10:42:01 AM UTC, comment #5: Thanks Jörg. Those warnings are getting quite irritating in eclipse when there are a lot of them!
|
Volker Kuhlmann <vok> |
Sat 29 Oct 2011 08:23:16 AM UTC, comment #4: As it's a GCC bug which has already been fixed there, and it only
|
Joerg Wunsch <joerg_wunsch> |
Sat 29 Oct 2011 04:36:20 AM UTC, comment #3: May I suggest to change the definition of PROGMEM for the buggy gcc versions as per the attached patch?
|
Volker Kuhlmann <vok> |
Sat 29 Oct 2011 01:06:21 AM UTC, comment #2: The approach of redefining PROGMEM to
|
Volker Kuhlmann <vok> |
Sun 07 Feb 2010 11:14:50 PM UTC, comment #1: Sorry, this is not an avr-libc bug but a GCC one. It has
|
Joerg Wunsch <joerg_wunsch> |
Sun 07 Feb 2010 11:01:18 PM UTC, original submission:
warning: only initialized variables can be placed into program memory area
|
Hose Bag <user> |
Depends on the following items: None found
Items that depend on this one: None found
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2011-10-29 | vok | Attached File | - | Added pgmspace.h.diff, #24236 | |
2010-02-07 | joerg_wunsch | Status | None | Invalid | |
Assigned to | None | joerg_wunsch | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-02a9.
Corresponding source code
I wasn't suggesting someone else do the backport, but I was wondering about my chances of success with applying the same patch you made for 4.6.2 to 4.3.3. Recompiling the source rpm shouldn't be too much of an issue.
What is the reason people are not upgrading to 4.6? 4.4 and 4.5 are not recommended (http://www.arduino.cc/playground/Learning/Linux).