public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Weddington, Eric" <Eric.Weddington@atmel.com>
To: "Georg-Johann Lay" <avr@gjlay.de>
Cc: <gcc-patches@gcc.gnu.org>, "Anatoly Sokolov" <aesok@post.ru>,
	       "Denis Chertykov" <chertykov@gmail.com>
Subject: RE: [Ping #2][Patch, testsuite]: Don't xfail sibcalls on AVR
Date: Wed, 06 Apr 2011 12:19:00 -0000	[thread overview]
Message-ID: <8D64F155F1C88743BFDC71288E8E2DA80134B3C4@csomb01.corp.atmel.com> (raw)
In-Reply-To: <4D9C466D.90507@gjlay.de>



> -----Original Message-----
> From: Georg-Johann Lay [mailto:avr@gjlay.de]
> Sent: Wednesday, April 06, 2011 4:55 AM
> To: Weddington, Eric
> Cc: gcc-patches@gcc.gnu.org; Anatoly Sokolov; Denis Chertykov
> Subject: Re: [Ping #2][Patch, testsuite]: Don't xfail sibcalls on AVR
> 
> >>> Target avr now supports tail calls, so don't xfail on that.
> >>>
> >>> testsuite/
> >>>
> >>> 2011-03-29  Georg-Johann Lay  <avr@gjlay.de>
> >>>
> >>> 	* gcc.dg/sibcall-3.c: Don't xfail on AVR.
> >>> 	* gcc.dg/sibcall-4.c: Don't xfail on AVR.
> >>>
> >
> > Please commit, Johann. Thanks.
> >
> > Eric
> 
> I don't have write privilege, and I don't think I want write access at
> the moment.

Oh! I didn't know. I thought you did.

Ok, let's see what I can do, then.

  reply	other threads:[~2011-04-06 12:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  9:38 [Ping][Patch, " Georg-Johann Lay
2011-04-05  9:06 ` [Ping #2][Patch, " Georg-Johann Lay
2011-04-05 23:01   ` Weddington, Eric
2011-04-06 10:54     ` Georg-Johann Lay
2011-04-06 12:19       ` Weddington, Eric [this message]
2011-04-06 12:55         ` Georg-Johann Lay
2011-04-06 23:26           ` Gerald Pfeifer
2011-04-08  9:30             ` Georg-Johann Lay
2011-04-09  7:30               ` Ralf Wildenhues
2011-04-09 15:40                 ` Gerald Pfeifer
2011-04-08 23:18 ` [Ping][Patch, " Weddington, Eric

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=8D64F155F1C88743BFDC71288E8E2DA80134B3C4@csomb01.corp.atmel.com \
    --to=eric.weddington@atmel.com \
    --cc=aesok@post.ru \
    --cc=avr@gjlay.de \
    --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).