Re: Question about simple_return pattern for the GCC ARM backend.
On 2013/12/28 09:31 AM, Yangfei (Felix) wrote: > Hi, > > I think that simple_return standard pattern is useful for the ARM. I mean > it should be good for target code performance. > But seems this pattern is not there for the GCC ARM backend. Can anyone > explain the reason why we don’t need this? > > Cheers, > Fei > It does use it. Search for the "return" expand pattern, and the "returns" code iterator in config/arm/iterators.md. Chung-Lin
Re: Remove spam in GCC mailing list
You want to send a mail to python-dev at python dot org. The spam still exists in gcc-bugs mailing list: http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg00689.html http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg00759.html http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg00776.html http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg01181.html http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg01586.html http://gcc.gnu.org/ml/gcc-bugs/2013-09/msg01513.html http://gcc.gnu.org/ml/gcc-bugs/2013-09/msg01946.html http://gcc.gnu.org/ml/gcc-bugs/2013-09/msg01947.html http://gcc.gnu.org/ml/gcc-bugs/2013-09/msg02011.html There's no reason that the gcc-bugs mailing list can post bug reports directly. Please delete spam messages from gcc-bugs. -- Tae-Wong Seo Korea, Republic of
gcc-4.7-20131228 is now available
Snapshot gcc-4.7-20131228 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20131228/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_7-branch revision 206233 You'll find: gcc-4.7-20131228.tar.bz2 Complete GCC MD5=5e96611f52dd4a9f1358bf4a5eac3349 SHA1=3f36bfeba2695e12c1bfa5cbcb8303bd62379def Diffs from 4.7-20131221 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.7 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
RE: Remove spam in GCC mailing list
Some background on the below: Google has recently changed its algorithms, and the presence of obvious spam mails pointing to a site now *lower* that site's Google rank. So the same "search engine optimization" people who created the spams for pay in the first place are now frantically trying to get the spams removed, to keep their clients from suing them. I think gcc is best served by just leaving the spams in the archive, as permanent punishment for the people who paid to wreck the Internet for their own gain. -Original Message- From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of Tae Wong Sent: Saturday, December 28, 2013 3:40 AM To: gcc@gcc.gnu.org Subject: Re: Remove spam in GCC mailing list You want to send a mail to python-dev at python dot org. The spam still exists in gcc-bugs mailing list: http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg00689.html http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg00759.html http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg00776.html http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg01181.html http://gcc.gnu.org/ml/gcc-bugs/2013-08/msg01586.html http://gcc.gnu.org/ml/gcc-bugs/2013-09/msg01513.html http://gcc.gnu.org/ml/gcc-bugs/2013-09/msg01946.html http://gcc.gnu.org/ml/gcc-bugs/2013-09/msg01947.html http://gcc.gnu.org/ml/gcc-bugs/2013-09/msg02011.html There's no reason that the gcc-bugs mailing list can post bug reports directly. Please delete spam messages from gcc-bugs. -- Tae-Wong Seo Korea, Republic of
