public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Georg-Johann Lay <avr@gjlay.de>
To: Denis Chertykov <chertykov@gmail.com>
Cc: Nathan Froyd <froydnj@codesourcery.com>,
	gcc-patches@gcc.gnu.org,  Anatoly Sokolov <aesok@post.ru>,
	Eric Weddington <eric.weddington@atmel.com>
Subject: Re: [Patch,AVR]: Fix PR45099
Date: Mon, 16 May 2011 15:53:00 -0000	[thread overview]
Message-ID: <4DD13487.50606@gjlay.de> (raw)
In-Reply-To: <BANLkTikcEjKyNvD7gXCJ6syJVV27oPEbzw@mail.gmail.com>

Denis Chertykov schrieb:
> 2011/5/6 Georg-Johann Lay <avr@gjlay.de>:
>> Nathan Froyd schrieb:
>>> On Mon, May 02, 2011 at 05:23:48PM +0200, Georg-Johann Lay wrote:
>>>> PR45099 is an extension that gives an error when a fixed register is
>>>> needed to pass a parameter to a function.
>>>>
>>>> Because the program will show malfunction when such code is generated,
>>>> anyway, I think an error is more appropriate than a warning (as
>>>> proposed in the PR).
>>> This seems like something that should be handled by common code.
>>>
>>> -Nathan
>> Yes, I agree. However, common code it too complicated for me to run
>> tests for, so I restrict myself to avr backend.
>>
>> Until such a test will find its way into common code, it might still
>> be useful in avr backend. I think this has quite low priority for
>> other targets because global registers are not very common in, e.g. i386.
>>
> 
> I think that better to have this patch.
> So, I approve it.

Ok, applied it as it was:
http://gcc.gnu.org/viewcvs?view=revision&revision=173791

> George, please make a working testcase against the trunk and post a
> GCC core bug.

How should such a testcase look like, and for what target? This is
highly target and ABI dependent. Moreover, the patch above just tests
for argument registers, not return registers.

Basically, I think of someone is hacking with global registers, he
must know what he is doing. There will always be cases where global
regs might violate some things if one is not careful.

Johann

> 
> Denis.
> 

  reply	other threads:[~2011-05-16 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 15:24 Georg-Johann Lay
2011-05-02 16:19 ` Nathan Froyd
2011-05-06 14:07   ` Georg-Johann Lay
2011-05-10 13:21     ` Denis Chertykov
2011-05-16 15:53       ` Georg-Johann Lay [this message]
2011-05-16 17:31         ` 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=4DD13487.50606@gjlay.de \
    --to=avr@gjlay.de \
    --cc=aesok@post.ru \
    --cc=chertykov@gmail.com \
    --cc=eric.weddington@atmel.com \
    --cc=froydnj@codesourcery.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).