Hi Stafford,
Some minor comments. I didn't read the atomics much, but I did look at
everything else, and it looks fine :-)
On Sat, Oct 27, 2018 at 01:37:02PM +0900, Stafford Horne wrote:
> +case ${target} in
> +or1k*-*-linux*)
> +tm_file="${tm_file} gnu-user.h
On 10/27/18 5:37 AM, Stafford Horne wrote:
> +(define_insn "zero_extendhisi2"
> + [(set (match_operand:SI 0 "register_operand""=r,r")
> + (zero_extend:SI (match_operand:HI 1 "nonimmediate_operand" "r,m")))]
> + ""
> + "@
> + l.exthz\t%0, %1
> + l.lhz\t%0, %1"
> +
On 10/27/18 5:36 AM, Stafford Horne wrote:
> Changes Since v2:
> - Add RTEMS patches from Joel Sherrill
> - Disable t-softfp-excl as suggsted by Joseph Myers
> - Add new architecture flags needed to run on real FPGA's found in testing
>* -mror - enable l.ror (rotate right)
>* -mshftimm
On 10/27/18 5:37 AM, Stafford Horne wrote:
> -mm-dd Stafford Horne
> Richard Henderson
>
> gcc/testsuite/ChangeLog:
>
> * gcc.c-torture/execute/20101011-1.c: Adjust for OpenRISC.
> * gcc.dg/20020312-2.c: Likewise.
> * gcc.dg/attr-alloc_size-11.c: Likewise.
>
On 10/27/18 5:37 AM, Stafford Horne wrote:
> +/* Here _init and _fini are empty because .init_array/.fini_array are used
> + exclusively. However, the functions are still needed as required when
> + linking. */
> + .align 4
> + .global _init
> + .type _init,@function
> +_init:
Hi,
Thanks for the review.
On Sat, Oct 27, 2018 at 06:25:04PM -0500, Segher Boessenkool wrote:
> Hi!
>
> On Sat, Oct 27, 2018 at 01:37:00PM +0900, Stafford Horne wrote:
> > + /* Given R = X * Y ... */
> > +1: l.sfeq r4, r0 /* while (y != 0) */
> > + l.bf
Hi!
On Sat, Oct 27, 2018 at 01:37:00PM +0900, Stafford Horne wrote:
> + /* Given R = X * Y ... */
> +1: l.sfeq r4, r0 /* while (y != 0) */
> + l.bf2f
> + l.andi r5, r4, 1 /* if (y & 1) ... */
Do the extra leading spaces
Hi,
In the testcase provided in the bug report, max value for niter
estimation is off by one when it is INTEGER_CST. As a results it
asserts at the place where it is checked for equality.
Attached patch fixes this. Bootstrapped and regression tested on
x86_64-linux-gnu with no new regression. Is
I've checked in this patch to fix a diagnostic message in the nios2
backend. This is in the target attribute parsing code; it now uses the
same wording as the similar diagnostic for an incorrect value given to
the corresponding command-line argument.
-Sandra
2018-10-27 Sandra Loosemore
Building GDB always builds the bundles libreadline.a, even if use of
the libreadline installed on the system was requested with --with-
system-readline.
The change below is for binutils-gdb’s/configure.ac, which is
maintained by gcc.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87741 [GCC]
I was triggered to do this by one of the comments in response to Anton
Shterenlikht's standards survey. The comment was sufficiently
inconsiderate that my first thought was not to respond. However,
curiosity got the better of me... so said the dead cat!
There is a lot of this patch but it is
On 10/22/18 6:45 PM, Peter Bergner wrote:
> Bah, my bootstrap failed and I need to make a small change. Let me do that
> and verify my bootstraps get all the way thru before I give you the updated
> patch. Sorry.
Ok, the following updated patch survives bootstrap and regtesting on
Hi Aaron,
On Sat, Oct 27, 2018 at 11:20:01AM -0500, Aaron Sawdey wrote:
> --- gcc/config/rs6000/rs6000.md (revision 265393)
> +++ gcc/config/rs6000/rs6000.md (working copy)
> @@ -2512,9 +2512,27 @@
>if (TARGET_POWERPC64 && TARGET_LDBRX)
> {
>if (MEM_P (src))
> -
At Segher's suggestion, I looked into changing the predicates on
bswapdi2_{load,store}
from memory_operand to indexed_or_indirect_operand and putting some code into
bswapdi2
to make the address indirect if it wasn't already.
The motivating case for this was the code I was seeing for the gpr
Hi,
On 2018-10-26 10:25 a.m., Jan Hubicka wrote:
>> From aea94273e7a477a03d1ee10a5d9043d6d13b8e8d Mon Sep 17 00:00:00 2001
>> From: Michael Ploujnikov
>> Date: Thu, 25 Oct 2018 13:16:36 -0400
>> Subject: [PATCH] Avoid unnecessarily numbering cloned symbols.
>>
>> gcc/ChangeLog:
>>
>> 2018-10-26
On 10/22/18 9:03 PM, Martin Sebor wrote:
> On 10/22/2018 09:08 AM, Bernd Edlinger wrote:
>> Hi!
>>
>> This makes c_strlen avoid an unsafe strlen folding of const arguments
>> with non-const offset. Currently a negative out of bounds offset
>> makes the strlen function return an extremely large
Am 23.10.18 um 23:02 schrieb Thomas Koenig:
So, I think this should be clear for trunk now. I will supply
the documentation later.
Ping ** 0.571428 ?
Originally, the idea about checking for missing location information
when not configured for release is to catch errors when adding new
code, so forgetting to add the info will show up right away on
regression testing.
From time to time, a user can stumble across something like that
and get a
Ping
> Le 20 oct. 2018 à 12:18, Romain Geissler a
> écrit :
>
> Hi,
>
> I would like to raise again the question of supporting -fuse-ld=ldd. A
> patch implementing it was already submitted in
> https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01722.html by Davide
> Italiano. This patch still
Use scalar operand in SF/DF/SI/DI vec_dup patterns which enables combiner
to generate
(set (reg:V8SF 84)
(vec_duplicate:V8SF (mem/c:SF (symbol_ref:DI ("y")
const_vector_duplicate_operand is added for constant vector broadcast.
We split
(set (reg:V16SF 86)
(const_vector:V16SF
20 matches
Mail list logo
