task.tw

Hi , We are own this domain name, have you made a decision to purchase it ? Looking forward to your reply. My admin e-mail: 2398...@qq.com Best regards, Alice

Re: Fail to compile GDB with recent GCC trunk (-Werror=stringop-overflow=, -Werror=stringop-truncation)

On 11/20/17, Eric Gallager wrote: > On 11/20/17, Yao Qi wrote: >> >> Hi, >> I failed to compile GDB with GCC trunk (8.0.0 20171117) because of some >> -Werror=stringop-overflow= and -Werror=stringop-truncation warnings. >> Some of them are not necessary to me, >> >> 1. ../../binutils-gdb/gdb/pyth

gcc-6-20171122 is now available

Snapshot gcc-6-20171122 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20171122/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6

gcc Bugzilla corrupt again?

I was adding a comment to bug: 81616 - Update -mtune=generic for the current Intel and AMD processors After clicking add comment it took me an an entirely different bug. I tried to add the comment again, and got a message about a "Mid Air Collision" The comment ended up the system twice (Com

Re: gcc Bugzilla corrupt again?

On Thu, Nov 23, 2017 at 1:51 AM, Andrew Roberts wrote: > I was adding a comment to bug: > > 81616 - Update -mtune=generic for the current Intel and AMD processors > > After clicking add comment it took me an an entirely different bug. > > I tried to add the comment again, and got a message about a

Re: gcc Bugzilla corrupt again?

On Thu, 23 Nov 2017, Jeffrey Walton wrote: On Thu, Nov 23, 2017 at 1:51 AM, Andrew Roberts wrote: I was adding a comment to bug: 81616 - Update -mtune=generic for the current Intel and AMD processors After clicking add comment it took me an an entirely different bug. I tried to add the comm