Jakub Jelinek writes:
> While working on Fedora gcc 9 rpm, I've noticed a couple of messages:
> *** WARNING:
> ./usr/src/debug/gcc-9.0.0-0.1.fc29.x86_64/libphobos/libdruntime/core/sys/posix/sys/ioccom.d
> is executable but has empty or no shebang,
> *** WARNING:
> ./usr/src/debug/gcc-9.0.0-0.1.f
Snapshot gcc-8-20190111 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20190111/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8
> While working on Fedora gcc 9 rpm, I've noticed a couple of messages:
> *** WARNING:
> ./usr/src/debug/gcc-9.0.0-0.1.fc29.x86_64/libphobos/libdruntime/core/sys/po
> six/sys/ioccom.d is executable but has empty or no shebang, *** WARNING:
> ./usr/src/debug/gcc-9.0.0-0.1.fc29.x86_64/libphobos/libdr
Hi!
While working on Fedora gcc 9 rpm, I've noticed a couple of messages:
*** WARNING:
./usr/src/debug/gcc-9.0.0-0.1.fc29.x86_64/libphobos/libdruntime/core/sys/posix/sys/ioccom.d
is executable but has empty or no shebang,
*** WARNING:
./usr/src/debug/gcc-9.0.0-0.1.fc29.x86_64/libphobos/libdrunt
Someone here was asking about GCC, ISL, and tiling and we looked at
the test gcc.dg/graphite/interchange-3.c on Aarch64. When this
test is run the graphite pass output file contains the string 'not
tiled' and since the dg-final scan-tree-dump is just looking for
the string 'tiled', it matches and
On 1/11/19 7:09 PM, Cao jin wrote:
> Hi Martin,
>>
>> and possibly for:
>> -mmemcpy-strategy
>>
>> and
>> -mstringop-strategy=alg
>>
>
> And yes, -mmemcpy-strategy worked as I expected.
typo. It is -mstringop-strategy=byte_loop
--
Sincerely,
Cao jin
Hi Martin,
On 1/11/19 5:22 PM, Martin Liška wrote:
> On 1/11/19 4:03 AM, Cao jin wrote:
>> Now the questions is: from code-reading, it is kind of non-intuitive, is
>> there any explicit way to control the optimization behavior accurately?
>
> Hi.
>
> Please take a look here:
> https://gcc.gnu.or
There was a bug which prevented building libgfortran. Now after the
issue is fixed, see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331,
I have posted new testresults.
https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg01052.html
Compared to rev. 265163 we have the following changes:
acats tes
On 1/11/19 4:03 AM, Cao jin wrote:
> Now the questions is: from code-reading, it is kind of non-intuitive, is
> there any explicit way to control the optimization behavior accurately?
Hi.
Please take a look here:
https://gcc.gnu.org/onlinedocs/gcc.pdf
you are searching for:
-mmemcpy
-mno-memcpy
