-09-29 Kelvin Nilsen
* gcc.target/powerpc/swaps-p8-30.c: Exchange the order of dg-do
and dg-require-effective-target directives to correct testing
behavior.
* gcc.target/powerpc/swaps-p8-32.c: Likewise.
* gcc.target/powerpc/swaps-p8-41.c: Likewise
Kelvin Nilsen
PR target/68972
* g++.dg/cpp1y/vla-initlist1.C: Add dg-skip-if directive to
disable this test on power architecture.
Index: gcc/testsuite/g++.dg/cpp1y/vla-initlist1.C
===
--- gcc/testsuite/g
this particular test case on power hardware.
The patch has been bootstrapped and tested on
powerpc64le-unknown-linux with no regressions.
Is this ok for trunk?
gcc/testsuite/ChangeLog:
2017-02-07 Kelvin Nilsen
PR target/68972
* g++.dg/cpp1y/vla-initlist1.C: Add dg-skip-if
This patch amends a patch merged with the trunk on 2017-01-14. One of
the new test cases added at that time has proven to be unreliable so
this path removes it.
Is this patch ok for trunk?
gcc/testsuite/ChangeLog:
2017-02-17 Kelvin Nilsen
PR target/78056
* gcc.target
in the PR 79395 report.
This patch has been bootstrapped and tested on
powerpc64le-unknown-linux with no regressions.
Is this ok for trunk?
gcc/ChangeLog:
2017-02-28 Kelvin Nilsen
PR target/79395
* config/rs6000/altivec.h (vec_ctz and others): Change the
preprocessor
patch, it was discovered that changes to the C++
templates representing the vec_all_ne and vec_any_eq built-in functions
were incomplete.
This patch has bootstrapped and been tested on
powerpc64le-unknown-linux with no regressions.
Is this ok for trunk?
gcc/ChangeLog:
2017-03-14 Kelvin Nilsen
Kelvin Nilsen
* config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Add
comments.
* config/rs6000/rs6000.c (rs6000_option_override_internal): Add
comments.
Index: gcc/config/rs6000/rs6000-c.c
TARGET_P9_VECTOR and !VECTOR_ELT_ORDER_BIG.
The patch has bootstrapped and tested on powerpc64le-unknown-linux-gnu
and powerpc64-unknown-linux-gnu with no regressions. Is this ok for GCC
7 when stage 1 opens?
Thanks.
--
Kelvin Nilsen, Ph.D. kdnil...@linux.vnet.ibm.com
home office: 801-756-4821
testing of P9 fusion instructions revealed a
problem with that particular code expansion. So this new revision of
the patch omits the fusion instruction generation pattern.)
Thanks.
gcc/testsuite/ChangeLog:
2016-03-17 Kelvin Nilsen
* gcc.target/powerpc/p9-permute.c: Generalize
I've added myself to the "Write After Approval" maintainers (Committed
revision 234526):
2016-03-29 Kelvin Nilsen
* MAINTAINERS (Write After Approval): Add myself.
--
Kelvin Nilsen, Ph.D. kdnil...@linux.vnet.ibm.com
home office: 801-756-4821, cell: 520-991
This trivial/obvious patch was committed without review as svn revision
240783. The patch fixes a compile-time error that recently surfaced
with big-endian Power architecture builds.
libcpp/ChangeLog:
2016-10-04 Kelvin Nilsen
PR target/77847
* lex.c (search_line_fast): Add
integration since
the error has broken the trunk for certain system configurations.
Is this patch ok for trunk?
gcc/ChangeLog:
2016-10-25 Kelvin Nilsen
PR target/78056
* config/rs6000/rs6000.c (spe_init_builtins): Modify loops to not
define builtin functions from the
or-subscript-2.c -O2 -flto
> -fno-use-linker-plugin -flto-partition=none execution test
> PASS: c-c++-common/torture/vector-subscript-2.c -O2 -flto
> -fuse-linker-plugin -fno-fat-lto-objects execution test
The patch has bootstrapped and regression tested on
powerpc64le-unknown-linux
-21 Kelvin Nilsen
* config/rs6000/rs6000.c (rs6000_option_override_internal): Add
comments to explain why certain error messages make mention of
undocumented options.
(rs6000_invalid_builtin): Change error messages to replace mention
of undocumented options
no regressions. Is
this ok for the trunk?
gcc/testsuite/ChangeLog:
2016-07-28 Kelvin Nilsen
* gcc.target/powerpc/bfp/bfp.exp: New file.
* gcc.target/powerpc/bfp/scalar-cmp-exp-eq-0.c: New test.
* gcc.target/powerpc/bfp/scalar-cmp-exp-eq-1.c: New test
of generated code, since the existing implementation
implicitly coerces the operand types to the declared type.
The patch has been bootstrapped and tested on powerpc64le-unknown-linux
without regressions.
Is this ok for the trunk?
gcc/ChangeLog:
2016-11-30 Kelvin Nilsen
PR target
for the trunk?
gcc/testsuite/ChangeLog:
2016-12-05 Kelvin Nilsen
* gcc.target/powerpc/byte-in-either-range-0.c: New test.
* gcc.target/powerpc/byte-in-either-range-1.c: New test.
* gcc.target/powerpc/byte-in-range-0.c: New test.
* gcc.target/powerpc/byte-in-range
and tested without regressions on
powerpc64le-unknown-linux and powerpc-unknown-linux (big-endian, with
both -m32 and -m64 target options) with no regressions.
Is this patch ok for trunk?
gcc/ChangeLog:
2016-12-08 Kelvin Nilsen
PR target/78056
* config/rs6000/rs6000.c: Provide
target options) with no regressions.
Is this ok for the trunk?
gcc/testsuite/ChangeLog:
2016-12-12 Kelvin Nilsen
* gcc.target/powerpc/byte-in-either-range-0.c: New test.
* gcc.target/powerpc/byte-in-either-range-1.c: New test.
* gcc.target/powerpc/byte-in-range-0.c: New
fail. They are checking that the compiler rejects those
programs with appropriate error messages.
On 12/13/2016 03:14 PM, Segher Boessenkool wrote:
> Hi Kelvin,
>
> On Mon, Dec 12, 2016 at 05:40:05PM -0700, Kelvin Nilsen wrote:
>> The patch has been bootstrapped and tested on
>>
known-linux and powerpc-unknown-linux (big-endian, with
both -m32 and -m64 target options) with no regressions.
Is this patch ok for trunk?
gcc/testsuite/ChangeLog:
2016-12-16 Kelvin Nilsen
PR target/78056
* gcc.target/powerpc/pr78056-1.c: New test.
* gcc.target/powe
-05-04 Kelvin Nilsen
* gcc.target/powerpc/darn-0.c: New test.
* gcc.target/powerpc/darn-1.c: New test.
* gcc.target/powerpc/darn-2.c: New test.
gcc/ChangeLog:
2016-05-04 Kelvin Nilsen
* config/rs6000/altivec.h: Add macro definitions for darn
against
the gcc-6-branch on both powerpc64le-unknown-linux-gnu and
powerpc64-unknown-linux-gnu with no regressions. Is this ok for trunk
and for backporting to GCC 6 after a few days of burn-in time on the trunk?.
Thanks,
Kelvin
gcc/testsuite/ChangeLog:
2016-05-04 Kelvin Nilsen
gcc-6-branch on both powerpc64le-unknown-linux-gnu and
powerpc64-unknown-linux-gnu with no regressions. Is this ok for trunk
and for backporting to GCC 6 after a few days of burn-in time on the
trunk?
Thanks,
Kelvin
gcc/testsuite/ChangeLog:
2016-05-11 Kelvin Nilsen
* gcc.target/p
?
gcc/testsuite/ChangeLog:
2016-11-14 Kelvin Nilsen
* gcc.target/powerpc/byte-in-either-range-0.c: New test.
* gcc.target/powerpc/byte-in-either-range-1.c: New test.
* gcc.target/powerpc/byte-in-range-0.c: New test.
* gcc.target/powerpc/byte-in-range-1.c: New
Thank you very much for the prompt and thorough review. There are a few
points below where I'd like to seek further clarification.
On 11/15/2016 04:19 AM, Segher Boessenkool wrote:
> Hi!
>
> On Mon, Nov 14, 2016 at 04:43:35PM -0700, Kelvin Nilsen wrote:
>> * conf
this over and over in define_expands?
>
The pattern I'm familiar with is to allocate the temporary scratch
register during expansion, and to use the allocated temporary at insn
match time. I'll have to teach myself a new pattern to do all of this
at insn match time. Feel free to po
nside toplev::main ()).
gcc/ChangeLog:
2016-01-14 Kelvin Nilsen
* toplev.c (do_compile): remove invocation of process_options ()
from within do_compile ()
(toplev::main): insert invocation of process_options () before
invocation of handle_common_deferred_options ().
101 - 128 of 128 matches
Mail list logo