On Wed, Jun 13, 2018 at 11:43 PM, Jonathan Wakely
wrote:
> Construct new elements before moving existing ones, so that if a default
> constructor throws, the existing elements are not left in a moved-from
> state.
>
> 2018-06-14 Daniel Trebbien
> Jonathan Wakely
>
> PR
Add multilib variants for -march=rv64imafd, e.g. to support the BOOMv2 core.
Add -mcmodel=medany as a variant of the 64-bit multilibs for RTEMS. The
ratinale for this change is that several existing RISC-V chips map the
RAM at 0x8000. In RTEMS, we do not use virtual memory, so
applications
Committed.
Thanks,
Roland
This patch adds HiSilicon's an mcpu: tsv110, which supports v8_4A.
---
gcc/ChangeLog| 8 +++
gcc/config/aarch64/aarch64-cores.def | 3 +
gcc/config/aarch64/aarch64-cost-tables.h | 103 +++
gcc/config/aarch64/aarch64-tune.md |
On Wed, Jun 13, 2018 at 5:52 PM, Roland McGrath wrote:
> A direct cherry-pick of the trunk change
> (db7548a2771bbf34cf7430712af7ac670b429958 / r259969) applies fine to
> today's 8 branch and has no check-gcc regressions on x86_64-linux-gnu.
>
> OK to commit to 8 branch now?
Sure.
Ian
A direct cherry-pick of the trunk change
(db7548a2771bbf34cf7430712af7ac670b429958 / r259969) applies fine to
today's 8 branch and has no check-gcc regressions on x86_64-linux-gnu.
OK to commit to 8 branch now?
Thanks,
Roland
In this testcase, the compiler is trying to evaluate a
constant-expression which involves a trivial defaulted copy
constructor. My patch for CWG 1581 had us instantiate any function
that appears in a potential constant expression, but that's not what
we want for a trivial constructor like this.
Construct new elements before moving existing ones, so that if a default
constructor throws, the existing elements are not left in a moved-from
state.
2018-06-14 Daniel Trebbien
Jonathan Wakely
PR libstdc++/83982
* include/bits/vector.tcc
The C implementation of the -Wbuiltin-declaration-mismatch
warning relies on TYPE_MODE to detect incompatibilities
between return and argument types in user declarations of
built-in functions. That prevents mistakes like
char* strlen (const char*);
from being detected (where sizeof (char*)
Great! Thanks, Steve.
On 13 June 2018 at 20:43, Steve Kargl wrote:
> Committed as obviously.
>
> 2018-06-13 Steven G. Kargl
>
> PR fortran/86110
> * array.c (gfc_resolve_character_array_constructor): Avoid NULL
> pointer dereference.
>
> 2018-06-13 Steven G. Kargl
>
On 06/13/2018 02:45 PM, Joseph Myers wrote:
This patch (commit r261518) has broken the build of the glibc testsuite.
I see, for example for aarch64-linux-gnu with build-many-glibcs.py:
In function 'test_strncat',
inlined from 'main' at tester.c:1621:3:
tester.c:490:13: error: 'strncat'
On Wed, Jun 13, 2018 at 05:21:55PM -0400, Michael Meissner wrote:
> In addition to the previous patch to aid in transitioning the PowerPC long
> double format to IEEE 128-bit, I have some additional patches that are needed.
> The previous patch is:
>
On Wed, Jun 13, 2018 at 5:08 PM, Jakub Jelinek wrote:
>
> On Wed, Jun 13, 2018 at 04:12:25PM -0400, Jason Merrill wrote:
> > On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
> > > The fix for 80178 was broken, because I forgot that copy_fn_p is false
> > > for move constructors. As a
In addition to the previous patch to aid in transitioning the PowerPC long
double format to IEEE 128-bit, I have some additional patches that are needed.
The previous patch is:
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00634.html
This patch fixes the power8 implementation of copysign for IEEE
In addition to the previous patch to aid in transitioning the PowerPC long
double format to IEEE 128-bit, I have some additional patches that are needed.
The previous patch is:
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00634.html
This patch prevents re-running the ibm128 and ieee128
In addition to the previous patch to aid in transitioning the PowerPC long
double format to IEEE 128-bit, I have some additional patches that are needed.
The previous patch is:
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00634.html
This fixes some of the PowerPC tests that had implicit
In addition to the previous patch to aid in transitioning the PowerPC long
double format to IEEE 128-bit, I have some additional patches that are needed.
The previous patch is:
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00634.html
This patch turns off setting the .gnu_attributes when building
On Wed, Jun 13, 2018 at 04:12:25PM -0400, Jason Merrill wrote:
> On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
> > The fix for 80178 was broken, because I forgot that copy_fn_p is false
> > for move constructors. As a result, the calling convention for a
> > class with a trivial move
On Wed, Jun 13, 2018 at 4:12 PM, Jason Merrill wrote:
> On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
>> The fix for 80178 was broken, because I forgot that copy_fn_p is false
>> for move constructors. As a result, the calling convention for a
>> class with a trivial move constructor
Hi Matthew,
> With one more change to add another comment as below, this is OK to
> commit.
>
> > @@ -18957,7 +19039,10 @@ mips_reorg_process_insns (void)
> > sequence and replace it with the delay slot instruction
> > then the jump to clear the forbidden slot
This patch (commit r261518) has broken the build of the glibc testsuite.
I see, for example for aarch64-linux-gnu with build-many-glibcs.py:
In function 'test_strncat',
inlined from 'main' at tester.c:1621:3:
tester.c:490:13: error: 'strncat' accessing 18446744073709551600 or more bytes
at
On Mon, Jun 11, 2018 at 09:22:27PM +0200, Thomas Koenig wrote:
>
> Regression-tested (which found one bug in the testsuite).
>
> OK for trunk?
>
I fine with the intent of the patch (see below).
PS: I think there may be some confusion on what IMPURE implies.
> Index: fortran/resolve.c
>
Am 13.06.2018 um 14:20 schrieb Janus Weil:
Hi Thomas,
the attached patch introduces the following changes:
thanks a lot for working on this!
If a logical .and. or .or. expression contains a reference to a
function
which is impure and which also does not behave like a pure function
(i.e.
This patch to the Go frontend by Than McIntosh fixes the compier to
avoid introducing redundant write barriers. The traversal used by the
write barrier insertion phase can sometimes wind up visiting new
statements inserted during the traversal, which then results in
duplicate / redundant write
Here is the missing part of the can_advance patch.
* include/debug/helper_functions.h
(__gnu_debug::_Safe_iterator<>): Add declaration.
(__can_advance(_Ite, _Size)): New.
(__can_advance(const _Safe_iterator<>&, _Size)): Overload declaration.
* include/debug/functions.h
On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
> The fix for 80178 was broken, because I forgot that copy_fn_p is false
> for move constructors. As a result, the calling convention for a
> class with a trivial move constructor and deleted copy constructor
> changed inappropriately.
This
gcc/testsuite/ChangeLog:
2018-06-13 Dimitar Dimitrov
* gcc.dg/tree-ssa/20040204-1.c: XFAIL on pru.
* gcc.dg/tree-ssa/reassoc-33.c: Ditto.
* gcc.dg/tree-ssa/reassoc-34.c: Ditto.
* gcc.dg/tree-ssa/reassoc-35.c: Ditto.
* gcc.dg/tree-ssa/reassoc-36.c:
gcc/testsuite/ChangeLog:
2018-06-13 Dimitar Dimitrov
* gcc.dg/stack-usage-1.c: Define PRU stack usage.
Signed-off-by: Dimitar Dimitrov
---
gcc/testsuite/gcc.dg/stack-usage-1.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.dg/stack-usage-1.c
Not all C language features are supported when -mabi=ti option is
used for PRU target.
gcc/testsuite/ChangeLog:
2018-06-13 Dimitar Dimitrov
* lib/gcc-dg.exp: Filter unsupported features in PRU's TI ABI mode.
* lib/target-utils.exp: Ditto.
Signed-off-by: Dimitar Dimitrov
---
On Wed, 13 Jun 2018, Dimitar Dimitrov wrote:
> + error ("__delay_cycles() only takes constant arguments");
As in documentation, diagnostics should not use () to indicate that a name
refers to a function (as opposed to referring to a call with no
arguments). However, function names,
Committed as obviously.
2018-06-13 Steven G. Kargl
PR fortran/86110
* array.c (gfc_resolve_character_array_constructor): Avoid NULL
pointer dereference.
2018-06-13 Steven G. Kargl
PR fortran/86110
* gfortran.dg/pr86110.f90: New test.
--
Steve
From: Dimitar Dimitrov
For some targets, Pmode != UNITS_PER_WORD. Take this into account
when marking hard registers as being used.
I tested C and C++ testsuits for x86_64 with and without this
patch. There was no regression, i.e. gcc.sum and g++.sum matched
exactly.
gcc/ChangeLog:
2018-06-13
On 06/13/2018 05:50 AM, Franz Sirl wrote:
>>>
>>>
>>> 2018-02-07 Franz Sirl
>>>
>>> * ira-build.c (object_range_compare_func): Stabilize sort.
>>> * tree-sra.c (compare_access_positions): Likewise.
>>> * varasm.c (output_object_block_compare): Likewise.
>>> *
Hi,
I would like to contribute a port for the TI PRU I/O processor [1], [2].
PRU is naturally 32-bit, but it is presented as 8-bit CPU for the GCC port.
This is needed in order to take advantage of the efficient PRU ISA modes
for addressing HW subregs [3].
The binutils port has been merged. I
PRU architecture supports maximum 256k program memory (IMEM). Some GCC
test cases manage to produce executables bigger than that.
gcc/testsuite/ChangeLog:
2018-06-13 Dimitar Dimitrov
* lib/gcc-dg.exp: Bail on region overflow for tiny targets.
* lib/target-utils.exp: Ditto.
The PRU load/store instructions can access memory with byte
granularity for all 30 of its 32-bit GP registers. Examples:
# Load 17 bytes from address r0[0] into registers r10.b1-r14.b2
lbbo r10.b1, r0, 0, 17
# Load 100 bytes from address r28[0] into registers r0-r25
lbbo r0.b0, r28,
The floating point support has been borrowed from C6X libgcc port
to help with TI PRU toolchain ABI compatibility.
libgcc/ChangeLog:
2018-06-13 Dimitar Dimitrov
* config.host: Add PRU target.
* config/pru/asri.c: New file.
* config/pru/eqd.c: New file.
*
gcc/testsuite/ChangeLog:
2018-06-13 Dimitar Dimitrov
* gcc.target/pru/abi-arg-struct.c: New test.
* gcc.target/pru/ashiftrt.c: New test.
* gcc.target/pru/builtins-1.c: New test.
* gcc.target/pru/builtins-error.c: New test.
* gcc.target/pru/clearbit.c:
gcc/testsuite/ChangeLog:
2018-06-13 Dimitar Dimitrov
* g++.old-deja/g++.abi/ptrmem.C: Add PRU to list.
Signed-off-by: Dimitar Dimitrov
---
gcc/testsuite/g++.old-deja/g++.abi/ptrmem.C | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
gcc/testsuite/ChangeLog:
2018-06-13 Dimitar Dimitrov
* gcc.c-torture/execute/20101011-1.c: Define DO_TEST to 0 for PRU.
* gcc.dg/20020312-2.c: No PIC register for PRU.
Signed-off-by: Dimitar Dimitrov
---
gcc/testsuite/gcc.c-torture/execute/20101011-1.c | 3 +++
Hi!
The following patch adds support for depend clause iterators.
Tested on x86_64-linux, committed to gomp-5_0-branch.
2018-06-13 Jakub Jelinek
* gimplify.c (gimplify_omp_depend): New function.
(gimplify_scan_omp_clauses): Gimplify depend clauses with iterators.
*
On 06/13/2018 09:16 AM, Jakub Jelinek wrote:
On Wed, Jun 13, 2018 at 08:53:20AM -0600, Martin Sebor wrote:
I'm actually worried about the fold-const.c change and don't understand, why
it has been done at all in the context of this PR.
case SAVE_EXPR:
if (flags &
This patch to the Go frontend by Than McIntosh includes global
variable preinit blocks in AST dumps. Each preinit block is prefixed
with a comment indicating the variable it is initializing.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
Index:
The C++ committee has confirmed that passing a null pointer to the
unary basic_string_view constructor is undefined. This removes the check
from our implementation, and adds the nonnull attribute to warn when the
compiler can detect undefined input.
Any objections to this change?
commit
Robert Suchanek writes:
> As already discussed, the link to the P6600 doesn't
> appear to be referenced on mips.com but reachable
> when searching for 'p6600':
>
> https://www.mips.com/downloads/p6600-multiprocessing-programmers-guide/
Thanks, good spot.
> gcc/ChangeLog:
>
> 2018-06-12
On 6/13/18, Matthew Fortune wrote:
> Hi,
>
> This patch was developed as part of preparing ever more complex multilib
> combinations for the MIPS architecture and aims to solve several problems
> in this area. I've attempted to be quite verbose in the description, so
> that I can explain how I am
On Wed, Jun 13, 2018 at 08:53:20AM -0600, Martin Sebor wrote:
> > I'm actually worried about the fold-const.c change and don't understand, why
> > it has been done at all in the context of this PR.
> >
> > case SAVE_EXPR:
> > if (flags & OEP_LEXICOGRAPHIC)
> > return
There is no need to use an allocator of the correct value_type when
calling allocator_traits::construct and allocator_traits::destroy. The
existing node allocator can be used, instead of constructing a new
allocator object every time.
There's also no benefit to using __gnu_cxx::__alloc_traits
This is needed for the ABSU_EXPR changes. It fixes a latent issue
in vect_recog_vector_vector_shift_pattern as well.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2018-06-13 Richard Biener
* tree-vect-patterns.c (vect_recog_vector_vector_shift_pattern):
On 06/13/2018 01:58 AM, Jakub Jelinek wrote:
On Wed, Jun 13, 2018 at 09:46:28AM +0200, Richard Biener wrote:
gcc/ChangeLog:
PR c/85931
* fold-const.c (operand_equal_p): Handle SAVE_EXPR.
gcc/testsuite/ChangeLog:
PR c/85931
* gcc.dg/Wstringop-truncation-3.c:
My tester flagged rl78 as failing to build due to a trivial error.
Specifically the rl78 backend was passing integer 0 as the flags
argument to print_rtl_with_bb. The argument should either be omitted
completely (there's an appropriate overload) or use TDF_NONE.
Fixed thusly. Verified the rl78
On Wed, Jun 13, 2018 at 07:06:23AM -0700, Cesar Philippidis wrote:
> Character variables in Fortran are slightly different than reals and
> integers because they can represent a single character or a string of
> them. Consequently, due their nature, the Fortran resolver requires more
> information
Character variables in Fortran are slightly different than reals and
integers because they can represent a single character or a string of
them. Consequently, due their nature, the Fortran resolver requires more
information to preform error checking on them.
PR85703 exposed an ICE when an OpenACC
Hi,
This patch was developed as part of preparing ever more complex multilib
combinations for the MIPS architecture and aims to solve several problems
in this area. I've attempted to be quite verbose in the description, so
that I can explain how I am using various terms as pretty much everyone
Prior to this patch, when the Fortran FE detected an invalid argument to
the OpenACC wait directive, it was trying to read the location of the
expression after it checked does not exist to error diagnostics. This
patch resolves that issue by reporting the error using %C.
I'll commit this patch to
This patch updates libgo to the 1.10.3 release. Bootstrapped and ran
Go testsuite on x86_64-pc-linux-gnu. Committed to mainline and GCC 8
branch.
Ian
Index: gcc/go/gofrontend/MERGE
===
--- gcc/go/gofrontend/MERGE (revision
On Tue, 2018-06-12 at 15:23 -0600, Jeff Law wrote:
> On 06/12/2018 03:16 PM, David Malcolm wrote:
> > On Tue, 2018-06-12 at 14:50 -0600, Jeff Law wrote:
> >
> > Ultimately these boil down to:
> >
> > gcc_checking_assert (INSN_P (rt)
> > || NOTE_P (rt)
> >
On Wed, 13 Jun 2018, Franz Sirl wrote:
> So, unless someone thinks one of the changes makes sense anyway, this patch is
> obsolete.
Yeah, I think that in light of gcc_qsort work this patch is completely
unnecessary now, and shouldn't be applied. In fact, reversing earlier
artificial stabilization
Hi Thomas,
>the attached patch introduces the following changes:
thanks a lot for working on this!
>If a logical .and. or .or. expression contains a reference to a
>function
>which is impure and which also does not behave like a pure function
>(i.e. does not have the implicit_pure attribute
On Mon, Jun 11, 2018 at 10:28 AM Kugan Vivekanandarajah
wrote:
>
> Hi Richard,
>
> Thanks for the review and sorry for getting back to you late.
>
> On 4 June 2018 at 18:38, Richard Biener wrote:
> > On Mon, Jun 4, 2018 at 10:18 AM Kugan Vivekanandarajah
> > wrote:
> >>
> >> Hi Richard,
> >>
>
Am 2018-06-12 um 23:49 schrieb Jeff Law:
On 02/07/2018 09:58 AM, Franz Sirl wrote:
Hi,
this is the result of an attempt to minimize the differences between the
compile results of a Linux-based and a Cygwin64-based powerpc-eabi cross
toolchain.
The method used was:
- find the
This is a follow-up to PR target/84763 present on mainline and 8 branch:
https://gcc.gnu.org/ml/gcc-patches/2018-03/msg00418.html
Since i386_pe_seh_cold_init now uses a small pre-allocation when there is
__builtin_{frame,return}_address in the function, it also may need to split
CFI save
On Fri, Jun 8, 2018 at 1:10 PM Martin Liška wrote:
>
> Hi.
>
> Second follow-up patch uses flags_from_decl_or_type in LTO merging
> of declarations. Hope it's more cleaner approach.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
That doesn't
Hi,
this patch adds lto-streamer-out dump file which journal what is streamed
into the output file and why. For example compiling:
#include
main()
{
fprintf (stderr, "Error\n");
}
We get
Creating compressed section .gnu.lto_.profile.3e57b5d44bc7b5b7
Creating output block for icf
Creating
From: Claudiu Zissulescu
This patch adds support for two ARCHS variations.
Ok to apply?
Claudiu
gcc/
2017-03-10 Claudiu Zissulescu
* config/arc/arc-arch.h (arc_tune_attr): Add new tune parameters
for ARCHS4x.
* config/arc/arc-cpus.def (hs4x): New cpu.
On Wed, Jun 13, 2018 at 10:51:41AM +0200, Richard Biener wrote:
> Your concern is for compile-time, not for correctness, right?
Yes.
> I think that
>
> /* If ARG0 and ARG1 are the same SAVE_EXPR, they are necessarily equal.
> We don't care about side effects in that case because the
Done. Thank you,
Claudiu
On Tue, Jun 12, 2018 at 10:32 PM, Andrew Burgess
wrote:
> * Claudiu Zissulescu [2018-05-21 13:18:38 +0300]:
>
>> Make sure only one operand has an immediate.
>>
>> OK to apply?
>
> Looks good.
>
> Thanks,
> Andrew
>
>> Claudiu
>>
>> gcc/
>> 2018-03-21 Claudiu
On Wed, 13 Jun 2018, Jakub Jelinek wrote:
> On Wed, Jun 13, 2018 at 10:22:29AM +0200, Jakub Jelinek wrote:
> > Random testcase for -Wduplicated-branches -fsanitize=shift:
> > int
> > foo (int x, int y)
> > {
> > if (x)
> > y = y << 1 >> 1 << 1 >> 1 << 1 >> 1 << 1 >> 1 << 1 >> 1 << 1 >> 1 <<
On Wed, Jun 13, 2018 at 10:22:29AM +0200, Jakub Jelinek wrote:
> Random testcase for -Wduplicated-branches -fsanitize=shift:
> int
> foo (int x, int y)
> {
> if (x)
> y = y << 1 >> 1 << 1 >> 1 << 1 >> 1 << 1 >> 1 << 1 >> 1 << 1 >> 1 << 1 >>
> 1 << 1 >> 1
> << 1 >> 1 << 1 >> 1 << 1
I've included and I updated the patch with your suggestions.
Thank you,
Claudiu
From: Andrew Burgess [andrew.burg...@embecosm.com]
Sent: Tuesday, June 12, 2018 10:10 PM
To: Claudiu Zissulescu
Cc: gcc-patches@gcc.gnu.org; francois.bed...@synopsys.com;
Committed. Thank you for your review,
Claudiu
From: Andrew Burgess [andrew.burg...@embecosm.com]
Sent: Tuesday, June 12, 2018 9:31 PM
To: Claudiu Zissulescu
Cc: gcc-patches@gcc.gnu.org; francois.bed...@synopsys.com;
claz...@synopsys.comq; claziss
Subject:
Committed. Thank you for your review,
Claudiu
From: Andrew Burgess [andrew.burg...@embecosm.com]
Sent: Tuesday, June 12, 2018 9:31 PM
To: Claudiu Zissulescu
Cc: gcc-patches@gcc.gnu.org; francois.bed...@synopsys.com;
claz...@synopsys.comq; claziss
Subject:
Done. Thank you for your review,
Claudiu
From: Andrew Burgess [andrew.burg...@embecosm.com]
Sent: Tuesday, June 12, 2018 9:32 PM
To: Claudiu Zissulescu
Cc: gcc-patches@gcc.gnu.org; francois.bed...@synopsys.com;
claz...@synopsys.comq; claziss
Subject: Re:
On Wed, Jun 13, 2018 at 09:58:49AM +0200, Jakub Jelinek wrote:
> I'm actually worried about the fold-const.c change and don't understand, why
> it has been done at all in the context of this PR.
>
> case SAVE_EXPR:
> if (flags & OEP_LEXICOGRAPHIC)
> return OP_SAME
Updated previous patch:
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00508.html
With coding style feedback from Richard Sandiford: (that also apply to this
patch)
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00508.html
Bootstrapped and tested on aarch64-linux-gnu. Okay for trunk?
On Wed, Jun 13, 2018 at 09:46:28AM +0200, Richard Biener wrote:
> > > > gcc/ChangeLog:
> > > >
> > > > PR c/85931
> > > > * fold-const.c (operand_equal_p): Handle SAVE_EXPR.
> > > >
> > > > gcc/testsuite/ChangeLog:
> > > >
> > > > PR c/85931
> > > > *
Updated with Richard's style and mismatched mode comments.
Okay for trunk?
-Original Message-
From: Richard Sandiford
Sent: Monday, June 11, 2018 11:47 AM
To: Michael Collison
Cc: James Greenhalgh ; GCC Patches
; nd
Subject: Re: [PATCH][Aarch64] v2: Arithmetic overflow addv patterns
On Tue, 12 Jun 2018, Martin Sebor wrote:
> On 06/11/2018 03:57 PM, Jeff Law wrote:
> > On 05/29/2018 08:57 PM, Martin Sebor wrote:
> > > Warning for a strncpy call whose bound is the same as the size
> > > of the source and suggesting to use the size of the source is
> > > less than helpful when
Hi,
On 06/10/2018 09:49 PM, Jakub Jelinek wrote:
> On Fri, Jun 08, 2018 at 08:10:40PM +0300, Denis Khalikov wrote:
>> From: Denis Khalikov
>> Date: Fri, 8 Jun 2018 19:53:01 +0300
>> Subject: [PATCH] PR sanitizer/86090
>>
>> * configure.ac: Check for lstat and readlink.
>> * configure,
Thanks for your comments, commited as r261538.
Paul Hua
On Tue, Jun 12, 2018 at 8:09 PM, Matthew Fortune wrote:
> Paul Hua writes:
>> The gcc.c-torture/execute/scal-to-vec1.c trigger a gcc ICE bug.
>>
>> It's a mistake in define_expand vec_setv4hi in loongson.md file.
>>
>> 375 (define_expand
On 2018-06-12 23:34, Olivier Hainque wrote:
>
>
>> On 12 Jun 2018, at 23:12, Jeff Law wrote:
>>
>> I'm going to defer to Olivier on all 6 parts of this kit. He knows
>> vxworks far better than I.
>
> No pb. I haven't forgotten about this :)
>
> As I mentioned on another
> thread, exceptions
81 matches
Mail list logo
