On 12/15/20 12:58 AM, Joseph Myers wrote:
Maybe change the script to use /sourceware/snapshot-tmp/gcc (which has
rather more space) instead of /tmp?
Jakub can you please do it?
Thanks,
Martin
g++-10 -v
Using built-in specs.
COLLECT_GCC=/opt/freeware/gcc-10.2.0/bin/g++-10
COLLECT_LTO_WRAPPER=/opt/freeware/gcc-10.2.0/libexec/gcc/powerpc-ibm-aix6.1.
9.0/10/lto-wrapper
Target: powerpc-ibm-aix6.1.9.0
Configured with: ../configure --prefix=/opt/freeware/gcc-10.2.0
--with-as=/usr/bin/as -
Hi,
I have some problems in gcc development about aarch64. I saw it doesn't support
V4QI machine mode in aarch64-modes.def, but it has V4QI in arm-modes.def.
I want to know why it doesn't?
I am looking forward your replies. Thanks for your help.
Best regards,
yancheng
Hi!
In a development branch based on devel/omp/gcc-10 branch (og10), which is
based on releases/gcc-10 branch, I'm running into the following issue.
But: the master branch code seems to look the same.
Given a specific scenario, we run into an ICE:
during GIMPLE pass: oaccdevlow
dump file
On Tue, Dec 15, 2020 at 05:02:24PM +0100, Thomas Schwinge wrote:
> Per the 'fold_convert_loc' code (cited below), we see that for 'type' of
> 'case INTEGER_TYPE' etc. -- which 'type' of 'case REFERENCE_TYPE' does
> "fall through" into -- we do not handle 'arg' of 'REAL_CST' like we do
> for 'type'
Hi!
I have updated my CC0 removal branch I started in 2019:
refs/users/segher/heads/cc0
(yes I know this needs some patch series work; this branch rebases).
I have tested it all on powerpc*, and sill test it with cross-compilers
to all Linux targets later today. I already know one problem that
On 12/15/20 10:27 AM, Segher Boessenkool wrote:
> Hi!
>
> I have updated my CC0 removal branch I started in 2019:
> refs/users/segher/heads/cc0
> (yes I know this needs some patch series work; this branch rebases).
>
> I have tested it all on powerpc*, and sill test it with cross-compilers
> t
