On 3/12/21 6:27 AM, Jakub Jelinek wrote:
On Mon, Mar 08, 2021 at 07:37:46PM -0700, Martin Sebor via Gcc-patches wrote:
Accesses to zero-length arrays continue to be diagnosed (except for
trailing arrays of unknown objects), as are nonempty accesses to empty
types.
The warning message for (3) re
On 3/12/21 6:52 AM, Jakub Jelinek wrote:
On Tue, Mar 09, 2021 at 03:07:38PM -0700, Martin Sebor via Gcc-patches wrote:
The gimple_call_alloc_size() function is documented to "return null
when STMT is not a call to a valid allocation function" but the code
assumes STMT is a call statement, causin
Hi!
As the patch shows, there are several bugs in
aarch64_simd_clone_compute_vecsize_and_simdlen.
One is that unlike for function declarations that aren't definitions
it completely ignores argument types. Such decls don't have DECL_ARGUMENTS,
but we can walk TYPE_ARG_TYPES instead, like the i386
On Fri, Mar 12, 2021 at 8:37 AM Uros Bizjak wrote:
>
> On Fri, Mar 12, 2021 at 2:20 PM H.J. Lu wrote:
> >
> > On Thu, Mar 11, 2021 at 11:21 PM Uros Bizjak wrote:
> > >
> > > On Thu, Mar 11, 2021 at 11:22 PM H.J. Lu wrote:
> > > >
> > > > Update 'P' operand modifier for -fno-plt to support inlin
Hi Iain,
Iain Buclaw via Gcc-patches wrote:
This patch fixes an ICE caused by emutls routines generating a weak,
non-public symbol for storing the initializer of a weak TLS variable.
In get_emutls_init_templ_addr, only declarations that were DECL_ONE_ONLY
would get a public initializer symbol
Hi,
This patch fixes an ICE caused by emutls routines generating a weak,
non-public symbol for storing the initializer of a weak TLS variable.
In get_emutls_init_templ_addr, only declarations that were DECL_ONE_ONLY
would get a public initializer symbol, ignoring variables that were
declared with
Hi Harald,
I am not sure of the etiquette for this - it looks OK to me :-)
Cheers
Paul
On Fri, 12 Mar 2021 at 21:20, Harald Anlauf via Fortran
wrote:
> Dear all,
>
> the addition of runtime checks for the SIZE intrinsic created a regression
> that showed up for certain CLASS arguments to pro
Hi!
The PR66728 changes broke __int128 handling.
It emits wide_int numbers in their minimum unsigned precision
rather than in their full precision.
The problem is then that e.g. the DW_OP_implicit_value path:
int_mode = as_a (mode);
loc_result = new_loc_descr (DW_OP_implicit_v
Hi!
E.g. on aarch64, the target has V2DImode addition and shift by scalar
optabs, but doesn't have V2DImode multiply. The following testcase
ICEs because this simplification is done after last lowering, but
generally, even if it is done before that, turning it into a multiplication
will not be an
