Besides simple pass-through (aggregate) jump function, arithmetic (aggregate)
jump function could also bring same (aggregate) value as parameter passed-in
for self-feeding recursive call. For example,
f1 (int i)/* normal jump function */
{
f1 (i & 1);
}
S
From: Andrew Pinski
vec_zeroextend.c fails on big-endian as it assumes
0 index is the lower part but it is not for
big-endian case. This fixes the problem by
using the correct index for the lower part
for big-endian.
Committed as obvious after a test on aarch64_be-linux-gnu.
Thanks,
Andrew Pin
Made some changes.
Feng
From: Feng Xue OS
Sent: Saturday, January 25, 2020 5:54 PM
To: mjam...@suse.cz; Jan Hubicka; gcc-patches@gcc.gnu.org
Subject: [PATCH] Generalized value pass-through for self-recursive function
(ipa/pr93203)
Besides simple pass-thr
Hi Tobias,
I hope my patch covers all issues. – OK for the trunk?
Yep.
Thanks a lot for the patch!
Regards
Thomas
Compared to the cc0 version, I noticed a regression in
delay-slot-filling for CRIS for several functions in libgcc with
a similar layout, one being lshrdi3, where with cc0 all
delay-slots were filled, as exposed by the test-case. I ended
up including the thankfully-small lshrdi3 as-is, for simplic
On Sat, 2020-01-25 at 15:14 +0100, Hans-Peter Nilsson wrote:
> Compared to the cc0 version, I noticed a regression in
> delay-slot-filling for CRIS for several functions in libgcc with
> a similar layout, one being lshrdi3, where with cc0 all
> delay-slots were filled, as exposed by the test-case.
In porting git trunk to hppa2.0w-hp-hpux11.11, I found that we lack defines for
SCNuMAX:
https://public-inbox.org/git/c9aa5047-7438-8f2f-985c-1c8771354...@bell.net/T/#u
This patch adds the missing defines.
Tested on hppa2.0w-hp-hpux11.11. Committed to trunk.
Dave
2020-01-25 John David Anglin
On Fri, Jan 24, 2020 at 10:39:14PM -0500, Jason Merrill wrote:
> [C++ PATCH] c++: is unnecessarily redundant, you can just write [PATCH].
True enough, I've dropped --subject-prefix from my git patch alias.
> On 1/24/20 6:20 PM, Marek Polacek wrote:> I neglected to add a proper
> diagnostic for th
On 23.01.20 21:09, Jeff Law wrote:
On Wed, 2020-01-22 at 22:23 +0100, Andreas Tobler wrote:
Hi all,
I'm digginig out old patches and I want to complete the libasan support
for FreeBSD x86_64. The below one was not that obvious when you have
been away for the past years.
In the last import the
On Fri, Jan 24, 2020 at 03:52:51PM -0700, Jeff Law wrote:
> When we thread through the successor of a joiner block we make a clone
> of the joiner block and redirect its outgoing edges. Of course if
> there's cases where we can't redirect an edge, then bad things will
> happen.
>
> The code alrea
On Sun, Jan 19, 2020 at 12:54:51PM +0100, Jan Hubicka wrote:
> > Bootstrapped/regtested on x86_64-linux and aarch64-linux.
> >
> > Feng
> > ---
> > 2020-01-19 Feng Xue
> >
> > PR ipa/93166
> > * ipa-cp.c (get_info_about_necessary_edges): Remove value
> > check assertion
Hi!
Apparently my recent patch which moved the *avx_vperm_broadcast* and
*vpermil* patterns before vpermpd broke the following testcase, the
define_insn_and_split matched always but the splitter condition only split
it if not -mavx2 for V4DFmode, basically relying on the vpermpd pattern to
come fi
Hi!
In the *{add,sub}v4_doubleword patterns, we don't really want to see a
VOIDmode last operand, because it then means invalid RTL
(sign_extend:{TI,POI} (const_int ...)) or so, and therefore something we
don't really handle in the splitter either. We have
*{add,sub}v4_doubleword_1 pattern for th
Here we crash when using -fsanitize=address -fdump-tree-sanopt because
the dumping code uses IDENTIFIER_POINTER on a null DECL_NAME. Instead,
we can print "" in such a case. Or we could avoid printing
that diagnostic altogether.
I don't think this warrants a testcase.
Tested x86_64-linux, ok fo
Here, we end up calling gen_type_die_with_usage for a type that's in the
middle of finish_struct_1, after we set TYPE_NEEDS_CONSTRUCTING on it but
before we copy all the flags to the variants--and, significantly, before we
set its TYPE_SIZE. It seems reasonable to only look at
TYPE_NEEDS_CONSTRUCT
warn_for_memset calls fold_for_warn, which calls fold_non_dependent_expr, so
also calling instantiate_non_dependent_expr here is undesirable.
Tested x86_64-pc-linux-gnu, applying to trunk.
PR c++/90997
* semantics.c (finish_call_expr): Don't call
instantiate_non_dependent_
16 matches
Mail list logo