From: Georg-Johann Lay <avr@gjlay.de>
To: "Weddington, Eric" <Eric.Weddington@atmel.com>
Cc: gcc-patches@gcc.gnu.org, Denis Chertykov <chertykov@gmail.com>,
Anatoly Sokolov <aesok@post.ru>
Subject: Re: [Patch,AVR]: Fix PR45263
Date: Mon, 04 Apr 2011 14:03:00 -0000 [thread overview]
Message-ID: <4D99CF65.3090002@gjlay.de> (raw)
In-Reply-To: <8D64F155F1C88743BFDC71288E8E2DA801268051@csomb01.corp.atmel.com>
Weddington, Eric schrieb:
>
>> -----Original Message-----
>> From: Georg-Johann Lay [mailto:avr@gjlay.de]
>> Sent: Friday, April 01, 2011 4:01 PM
>> To: Georg-Johann Lay
>> Cc: gcc-patches@gcc.gnu.org; Denis Chertykov; Anatoly Sokolov; Weddington,
>> Eric
>> Subject: Re: [Patch,AVR]: Fix PR45263
>>
>> This is a better fix that does not need push/pop and does not increase
>> numer of instructions.
>>
>> r16 takes the role of r20, and the value formerly in r16,
>> i.e. hh8(__dtors_end resp. __ctors_start) is recreated as needed.
>>
>
> Hi Johann,
>
> Have you tested this patch against the test case in bug #45263?
avr-gcc still aborts on building avr-libc as of
http://gcc.gnu.org/ml/gcc/2011-04/msg00008.html
Using avr-gdb-7.2 to debug with stubs runs on errors and doesn't show
me any code... no assembly with "A syntax error in expression, near
`0x29c'" in assembly window.
Trying to compile with avr-gcc and dwarf crashes avr-gcc.
__do_copy_data fails to initialize var1 and var2 (are 0x0).
Too much is broken... giving up.
Johann
next prev parent reply other threads:[~2011-04-04 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 18:20 Georg-Johann Lay
2011-04-01 22:06 ` Georg-Johann Lay
2011-04-01 22:29 ` Weddington, Eric
2011-04-04 14:03 ` Georg-Johann Lay [this message]
2011-04-06 13:30 ` Georg-Johann Lay
2011-04-11 17:05 ` Ping: " Georg-Johann Lay
2011-04-12 5:35 ` Denis Chertykov
2011-05-27 16:41 ` [Patch, 4.6, AVR]: " Georg-Johann Lay
2011-05-27 18:42 ` Denis Chertykov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D99CF65.3090002@gjlay.de \
--to=avr@gjlay.de \
--cc=Eric.Weddington@atmel.com \
--cc=aesok@post.ru \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).