Re: [PATCH, LIBGCC] Avoid count_leading_zeros with undefined result (PR 78067)

On 10/28/16 16:05, Bernd Edlinger wrote: > On 10/27/16 22:23, Joseph Myers wrote: >> On Thu, 27 Oct 2016, Bernd Edlinger wrote: >> >>> Hi, >>> >>> by code reading I became aware that libgcc can call count_leading_zeros >>> in certain cases which can give undefined results. This happens on >>>

Re: [PATCH v3] gcc/config/tilegx/tilegx.c (tilegx_function_profiler): Save r10 to stack before call mcount

Firstly, sorry for replying late (During these days, I worked overtime every workday, and have to reply in weekend). On 10/24/16 23:27, Jeff Law wrote: > On 10/23/2016 12:11 PM, Bernd Edlinger wrote: >> Hi, >> >> I don't know much about tilegx, but >> I think the patch should work as is. >> >>

One more issue with vax and spu ports with current trunk

REGNO_REG_CLASS is defined as: #define REGNO_REG_CLASS(REGNO) ALL_REGS For the vax port and in a similar manner on the spu port. Note how it doesn't use the REGNO argument. This causes problems for the new noop set code: /* Detect noop sets and remove them before processing side

RFD: Buffer handling for ASM_GENERATE_INTERNAL_LABEL

Consider this definition of ASM_GENERATE_INTERNAL_LABEL (from sp64-elf.h): #undef ASM_GENERATE_INTERNAL_LABEL #define ASM_GENERATE_INTERNAL_LABEL(LABEL,PREFIX,NUM) \ sprintf ((LABEL), "*.L%s%ld", (PREFIX), (long)(NUM)) And a use from assemble_static_space: ASM_GENERATE_INTERNAL_LABEL

Contents of PO file 'cpplib-6.1.0.eo.po'

cpplib-6.1.0.eo.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator.

New Esperanto PO file for 'cpplib' (version 6.1.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'cpplib' has been submitted by the Esperanto team of translators. The file is available at: http://translationproject.org/latest/cpplib/eo.po (This file,

[Committed] PR fortran/71891 -- Fix obvious typo

I've committed the following to both 6-branch and trunk. 2016-10-28 Steven G. Kargl PR fortran/71891 * symbol.c (gfc_type_compatible): Fix typo. Index: symbol.c === --- symbol.c(revision

Go patch committed: copy slice from Go 1.7 runtime

This patch to the compiler and libgo copies the slice support from the Go 1.7 runtime. This changes the Go frontend to handle append as the gc compiler does: call a function to grow the slice, but otherwise assign the new elements directly to the final slice. For the current gccgo memory

Re: [PATCH] fix linker name for uClibc

On 10/28/2016 11:14 AM, Waldemar Brodkorb wrote: Hi, uClibc-ng can be used for Microblaze architecture. It is regulary tested with qemu-system-microblaze in little and big endian mode. 2016-10-28 Waldemar Brodkorb gcc/ * config/microblaze/linux.h: add

Re: [Patch 1/11] Add a new target hook for describing excess precision intentions

On Fri, 14 Oct 2016, James Greenhalgh wrote: > + value set for @code{-fexcess-precision=[standard|fast]}.", I think the correct markup for the option here is: @option{-fexcess-precision=@r{[}standard@r{|}fast@r{]}} (that is, using @option not @code, and with the [ | ] not in a fixed-width

Re: [Patch 6/11] Migrate excess precision logic to use TARGET_EXCESS_PRECISION

On Fri, 14 Oct 2016, James Greenhalgh wrote: > +/* If the join of the implicit precision in which the target will compute > + floating-point values and the standard precision in which the target will > + compute values is not equal to the standard precision, then the target > + is either

Re: [PATCH] Delete GCJ

> Things we may want to remove: > > - references to java in contrib (download_ecj, gcc_update, > patch_tester.sh, update-copyright.py) > - GCJ, GCJ_FOR_BUILD, GCJ_FOR_TARGET in Makefiles.tpl and configure.ac > - LIBGCJ_SONAME in config/i386/{cygwin.h,mingw32.h} > - references to java in

libgo patch committed: Fix time test for recent timezone data update

This libgo patch fixes the time test for systems that using the recent tzdata-2016g update, which added a new zone abbreviation. Bootstrapped and ran time test on x86_64-pc-linux-gnu. Committed to mainline and GCC 6 branch. Ian Index: gcc/go/gofrontend/MERGE

Re: [PATCH, libgo]: Fix FAIL: time testsuite failure

On Tue, Oct 18, 2016 at 2:19 AM, Uros Bizjak wrote: > The name of Etc/GMT+1 timezone is "-01", as evident from: > > $ TZ=Etc/GMT+1 date +%Z > -01 > > Attached patch fixes the testsuite failure. Thanks--I'm going to copy the change made to the master library instead. Will

Default associative containers constructors/destructor/assignment

Hi Here is the patch to default all other associative containers operations that can be defaulted. To do so I introduce a _Rb_tree_key_compare type that take care of value initialization of compare functor. It also make sure that functor is copied rather than move in move

Re: [PATCH] Fix filesystem::path for iterators with const value_type

On Fri, Oct 28, 2016 at 1:47 PM, Jonathan Wakely wrote: > For some reason the Filesystem library says that you can construct > paths from iterators with value_type that is a possibly const encoded > character type. I don't know why we support const value_type in this > place,

Re: RFC [1/3] divmod transform v2

On 26 October 2016 at 16:17, Richard Biener wrote: > On Wed, 26 Oct 2016, Prathamesh Kulkarni wrote: > >> On 25 October 2016 at 18:47, Richard Biener wrote: >> > On Tue, 25 Oct 2016, Prathamesh Kulkarni wrote: >> > >> >> On 25 October 2016 at 16:17, Richard

[PATCH 1/3] use rtx_insn * in various places where it is obvious

From: Trevor Saunders gcc/ChangeLog: 2016-10-27 Trevor Saunders * config/arc/arc.c (arc_emit_call_tls_get_addr): Make the type of variables rtx_insn *. * config/arm/arm.c (arm_call_tls_get_addr): Likewise.

[PATCH 3/3] split up some variables to use rtx_insn * more

From: Trevor Saunders Note to readers, a -b diff is below the whitespace sensitive one and should be much easier to read. gcc/ChangeLog: 2016-10-27 Trevor Saunders * config/alpha/alpha.c (alpha_legitimize_address_1): Split up

[PATCH 0/3] use rtx_insn * more

From: Trevor Saunders HI, This series changes various variables type from rtx to rtx_insn * so that the remaining patches in this series http://gcc.gnu.org/ml/gcc-patches/2016-10/msg01353.html can be applied. patches bootstrapped and regtested on x86_64-linux-gnu,

[PATCH 2/3] split up the trial variable in reorg.c:relax_delay_slots to use rtx_insn * more

From: Trevor Saunders gcc/ChangeLog: 2016-10-27 Trevor Saunders * reorg.c (relax_delay_slots): Split up the trial variable. --- gcc/reorg.c | 19 +-- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git

libgo patch committed: add missing build tag

This patch to libgo adds a missing build tag to runtime/flstack_32bit.go, fixing the build on 32-bit PPC. This should fix GCC PR 78143. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu, which admittedly does not have the problem. Committed to mainline. Ian Index: gcc/go/gofrontend/MERGE

Re: [SPARC] Add support for overflow arithmetic

On Fri, Oct 28, 2016 at 07:27:56PM +0200, Eric Botcazou wrote: > Thanks for the hint. The hook is the way to go I think because BITS_PER_WORD > is not a constant, so the default would not be properly initialized. Here's > a > tentative patch, I'll add a couple of SPARC-specific testcases if

[PATCH] Make filesystem::path work with basic_string_view (P0392R0)

This integrates string_view with experimental::filesystem::path, which is not actually in the TS, but is required for std::filesystem. I've made it work with experimental::string_view in C++14 mode, and with std::string_view in C++17 mode. I suppose I could have made it work with either in C++17

[PATCH] fix linker name for uClibc

Hi, uClibc-ng can be used for Microblaze architecture. It is regulary tested with qemu-system-microblaze in little and big endian mode. 2016-10-28 Waldemar Brodkorb gcc/ * config/microblaze/linux.h: add UCLIBC_DYNAMIC_LINKER diff --git

Re: [PATCH] Fix PR77407

On Wed, 28 Sep 2016, Richard Biener wrote: The following patch implements patterns to catch x / abs (x) and x / -x, taking advantage of undefinedness at x == 0 as opposed to the PR having testcases with explicit != 0 checks. Bootstrap / regtest pending on x86_64-unknown-linux-gnu. Richard.

Re: [Aarch64] Variant field

On Fri, Oct 28, 2016 at 10:50 AM, Benedikt Huber wrote: > Hi, > > In the aarch64 backend we would need VARIANT field in AARCH64_CORE to specify > and detect > variants of xgene. > > I found this patch of Andrew Pinski >

libgo patch committed: redirect mkrsysinfo.sh grep output to /dev/null

This patch to libgo redirects the output of a grep command in mkrsysinfo.sh to /dev/null. The output otherwise appears in the middle of a build log, where it is harmless but confusing. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian Index:

[Aarch64] Variant field

Hi, In the aarch64 backend we would need VARIANT field in AARCH64_CORE to specify and detect variants of xgene. I found this patch of Andrew Pinski https://gcc.gnu.org/ml/gcc-patches/2015-11/msg02148.html However it did not find its way to trunk. Why was that the case? What is the correct way

[PATCH] Fix filesystem::path for iterators with const value_type

For some reason the Filesystem library says that you can construct paths from iterators with value_type that is a possibly const encoded character type. I don't know why we support const value_type in this place, when normally that is bogus (even const_iterators have a non-const value_type, and

Re: [PR debug/77773] segfault when compiling __simd64_float16_t with -g

On October 28, 2016 6:46:07 PM GMT+02:00, Aldy Hernandez wrote: >On 10/28/2016 01:40 AM, Richard Biener wrote: >> On Thu, Oct 27, 2016 at 6:14 PM, Aldy Hernandez >wrote: >>> On 10/27/2016 12:35 AM, Richard Biener wrote: On Wed, Oct 26, 2016 at 9:17

Re: [SPARC] Add support for overflow arithmetic

> Then to some extent defining WORD_REGISTER_OPERATIONS on SPARC is a lie, > it only has "INT_REGISTER_OPERATIONS", i.e. all operations smaller than > int are performed on the whole register, int operations can be really done > in SImode in the IL (no need to sign/zero extend anything to DImode,

Re: [PR debug/77773] segfault when compiling __simd64_float16_t with -g

On 10/28/2016 01:40 AM, Richard Biener wrote: On Thu, Oct 27, 2016 at 6:14 PM, Aldy Hernandez wrote: On 10/27/2016 12:35 AM, Richard Biener wrote: On Wed, Oct 26, 2016 at 9:17 PM, Aldy Hernandez wrote: The following one-liner segfaults on arm-eabi when

[gomp4] propagating conditionals in worker-vector partitioned loops

I've applied the patch to gomp-4_0-branch to correct an issue involving the propagation of variables used in conditional expressions to worker and vector partitioned loops. More details regarding this patch can be found here Cesar

Re: Ping: Re: [PATCH 1/2] gcc: Remove unneeded global flag.

* Jeff Law [2016-10-28 09:58:14 -0600]: > On 09/15/2016 08:24 AM, Andrew Burgess wrote: > > * Jakub Jelinek [2016-09-14 15:07:56 +0200]: > > > > > On Wed, Sep 14, 2016 at 02:00:48PM +0100, Andrew Burgess wrote: > > > > In an attempt to get this patch merged

Re: [PATCHv2 4/7, GCC, ARM, V8M] ARMv8-M Security Extension's cmse_nonsecure_entry: clear registers

On 27/10/16 11:44, Kyrill Tkachov wrote: > > On 27/10/16 11:00, Andre Vieira (lists) wrote: >> On 26/10/16 17:30, Kyrill Tkachov wrote: >>> On 26/10/16 17:26, Andre Vieira (lists) wrote: On 26/10/16 13:51, Kyrill Tkachov wrote: > Hi Andre, > > On 25/10/16 17:29, Andre Vieira

Re: [PATCH][AArch64] Add a SHA1H pattern

On Fri, Oct 28, 2016 at 04:54:05PM +0100, Wilco Dijkstra wrote: > James Greenhalgh wrote: > > On Wed, Oct 26, 2016 at 12:11:44PM +, Wilco Dijkstra wrote: > > > Add a SHA1H pattern with a V2SI input.  This avoids unnecessary > > > DUPs when using intrinsics like vsha1h_u32 (vgetq_lane_u32 (x,

Re: [patch,testsuite] Support dg-require-effective-target label_offsets.

On Oct 27, 2016, at 3:16 AM, Georg-Johann Lay wrote: > > Now imagine some arithmetic like & - & This might result in one > or two stub addresses, and difference between such addresses is a complete > different thing than the difference between the original labels: The result

Re: Ping: Re: [PATCH 1/2] gcc: Remove unneeded global flag.

On 09/15/2016 08:24 AM, Andrew Burgess wrote: * Jakub Jelinek [2016-09-14 15:07:56 +0200]: On Wed, Sep 14, 2016 at 02:00:48PM +0100, Andrew Burgess wrote: In an attempt to get this patch merged (as I still think that its correct) I've investigated, and documented a little

Re: [PATCH][AArch64] Add a SHA1H pattern

James Greenhalgh wrote: > On Wed, Oct 26, 2016 at 12:11:44PM +, Wilco Dijkstra wrote: > > Add a SHA1H pattern with a V2SI input.  This avoids unnecessary > > DUPs when using intrinsics like vsha1h_u32 (vgetq_lane_u32 (x, 0)). > > I think this is incorrect for big endian - element 0 of a

Re: [RFA] Fix various PPC build failures due to int-in-boolean-context code

On Fri, Oct 28, 2016 at 09:12:29AM -0600, Jeff Law wrote: > * config/rs6000/rs6000.c (rs6000_option_override_internal): Avoid > false positive from int-in-boolean-context warnings. > > diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c > index 5e35e33..38a5226 100644

Fix bfin port WRT fallthru warnings

These were pretty obvious when looking at the code. Verified the bfin ports from config-list.mk will build with a trunk compiler. Installing on the trunk. Now onward to the target independent bits (which are few). Jeff commit 71012b1c342ab2b69494429ec2d60d94248acea5 Author: law

Re: [RFA] Fix various PPC build failures due to int-in-boolean-context code

On 10/28/2016 09:17 AM, Jakub Jelinek wrote: On Fri, Oct 28, 2016 at 09:12:29AM -0600, Jeff Law wrote: * config/rs6000/rs6000.c (rs6000_option_override_internal): Avoid false positive from int-in-boolean-context warnings. diff --git a/gcc/config/rs6000/rs6000.c

[RFA] Fix various PPC build failures due to int-in-boolean-context code

The PPC port is stumbling over the new integer in boolean context warnings. In particular this code from rs6000_option_override_internal is problematical: HOST_WIDE_INT flags = ((TARGET_DEFAULT) ? TARGET_DEFAULT :

Re: MAINTAINERS update

Hi, I added myself to the MAINTAINERS file (Write After Approval) on 10/27/2016. The commit was r241636. Sorry, forgot the patch the first time. Carl Love Index: ChangeLog === --- ChangeLog (revision 241636) +++

MAINTAINERS update

Hi, I added myself to the MAINTAINERS file (Write After Approval) on 10/27/2016. The commit was r241636. Carl Love

[PATCH] Implement std::filesystem for C++17

Here's a patch to move std::experimental::filesystem to std::filesystem, and then add using declarations to pull it all back into std::experimental::filesystem. The definitions are still in the separate libstdc++fs.a archive, not in libstdc++.so, and I plan to keep it that for GCC 7, because

Re: [PATCH] sched: Do not mix prologue and epilogue insns

On 10/28/2016 03:37 PM, Segher Boessenkool wrote: This patch makes scheduling not reorder prologue insns relative to epilogue insns and vice versa. This fixes PR78029. This seems good to me. Bernd

Re: [PATCH] Fix and testcases for pr72747

On Fri, 2016-10-28 at 08:31 -0500, Will Schmidt wrote: > On Fri, 2016-10-28 at 10:38 +0200, Richard Biener wrote: > > On Thu, Oct 27, 2016 at 5:37 PM, Will Schmidt > > wrote: > > > Hi, > > > > > > Per PR72747, A statement such as "v = vec_splats (1);" correctly > > >

Re: [PATCH] GIMPLE store merging pass

On 27/10/16 14:31, Richard Biener wrote: On Mon, 24 Oct 2016, Kyrill Tkachov wrote: Hi all, This is a slight update over [1] with Richard's feedback addressed. In terminate_all_aliasing_chains we now terminate the chain early if the destination is writing to a base offset by a variable

[PATCH] Implement std::launder for C++17

This implements std::launder, using Jakub's new __builtin_launder. In order to allow our headers to be used with Clang (which doesn't implement all our new built-ins yet) I've added a couple of checks using Clang's __has_builtin. My initial version of std::launder used

Re: [PATCH, LIBGCC] Avoid count_leading_zeros with undefined result (PR 78067)

On 10/27/16 22:23, Joseph Myers wrote: > On Thu, 27 Oct 2016, Bernd Edlinger wrote: > >> Hi, >> >> by code reading I became aware that libgcc can call count_leading_zeros >> in certain cases which can give undefined results. This happens on >> signed int128 -> float or double conversions, when

Re: Fix PR77309, combine eliminates sign bit comparison

Hi Bernd, On Fri, Oct 28, 2016 at 01:18:19PM +0200, Bernd Schmidt wrote: > In this PR, we manage to simplify the code down to > > (lt (and (reg) (signbit)) (const 0)) > > simplify_comparison then calls make_compound_operation on the AND > expression, and that turns it into a ZERO_EXTRACT of a

[PATCH] sched: Do not mix prologue and epilogue insns

This patch makes scheduling not reorder prologue insns relative to epilogue insns and vice versa. This fixes PR78029. The problem in that PR: We have two insns, in this order: (insn/f 300 299 267 8 (set (reg:DI 65 lr) (reg:DI 0 0)) 579 {*movdi_internal64} (expr_list:REG_DEAD

Re: [PATCH] Fix and testcases for pr72747

On Fri, 2016-10-28 at 10:38 +0200, Richard Biener wrote: > On Thu, Oct 27, 2016 at 5:37 PM, Will Schmidt > wrote: > > Hi, > > > > Per PR72747, A statement such as "v = vec_splats (1);" correctly > > initializes a vector. However, a statement such as "v[1] = v[0] = > >

Re: [PATCH] Fix computation of register limit for -fsched-pressure

On 10/28/2016 06:38 AM, Bin.Cheng wrote: > On Fri, Oct 28, 2016 at 12:27 PM, Tamar Christina > wrote: >> > Looking at it again, >> > >> > it seems to be that the testcase should be adjusted. >> > There's no actual spilling. It just uses more registers than before due to

[PATCH] Fix PR78128

The following fixes a mistake in an earlier patch of mine fixing PR71002. fold-const.c make_bit_field_ref doesn't care about alias sets of references it merges but as it commons to a common base it assumed the original refs were aliased by the new one. The testcase of PR71002 shows this is not

Re: [patch,testsuite] Support dg-require-effective-target label_offsets.

On 27.10.2016 12:49, Bernd Schmidt wrote: On 10/27/2016 12:16 PM, Georg-Johann Lay wrote: Now imagine some arithmetic like & - & This might result in one or two stub addresses, and difference between such addresses is a complete different thing than the difference between the original labels:

Re: [PATCH VECT]Skip unnecessary data dependence check after visited store stmt in slp

On Fri, Oct 28, 2016 at 1:10 PM, Bin Cheng wrote: > Hi, > Function vect_slp_analyze_node_dependences delays data-dependence check for > visited store stmts until we run into the last store, because all stores are > sunk/vectorized at the position of the last one. The problem

Re: [PATCH VECT]Swap operands for cond_reduction when necessary

On Wed, Oct 26, 2016 at 6:42 PM, Bin Cheng wrote: > Hi, > For stmt defining reduction, GCC vectorizer assumes that the reduction > variable is always the last (second) operand. Another fact is that > vectorizer doesn't swap operands for cond_reduction during analysis stage.

Re: [PATCH VECT]Support operand swapping for cond_expr in vect_slp

On Thu, Oct 27, 2016 at 3:37 PM, Bin Cheng wrote: > Hi, > During analysis, vect_slp checks if statements of a group are isomorphic to > each other, specifically, all statements have to be isomorphic to the first > one. Apparently, operands of commutative operators

[PATCH][0/2] GIMPLE Frontend

I've posted two patches implementing a GIMPLE Frontend to the extent required for simple unit testing of GIMPLE passes. The work was mostly done by Prasad Ghangal during this years GSoC project. I've picked it up to ensure it would be ready for the end of stage1 even though the frontend itself

[PATCH][2/2] GIMPLE Frontend, middle-end changes

These are the middle-end changes and additions to the testsuite. They are pretty self-contained, I've organized the changelog entries below in areas of changes: 1) dump changes - we add a -gimple dump modifier that allows most function dumps to be directy fed back into the GIMPLE FE 2) pass

[PATCH][1/2] GIMPLE Frontend, C FE parts (and GIMPLE parser)

These are the C (and ObjC) Frontend changes required by the GIMPLE Frontend which is now itself contained in c/gimple-parser.[ch]. Most changes are due to a new c-parser.h header where we export stuff from the C parser that the GIMPLE frontend requires. Other changes include new __GIMPLE and

Re: [PATCH] Fix computation of register limit for -fsched-pressure

On Fri, Oct 28, 2016 at 12:27 PM, Tamar Christina wrote: > Looking at it again, > > it seems to be that the testcase should be adjusted. > There's no actual spilling. It just uses more registers than before due to > the scheduling. Sorry I didn't look into the test, but

Re: [PATCH] Fix computation of register limit for -fsched-pressure

Looking at it again, it seems to be that the testcase should be adjusted. There's no actual spilling. It just uses more registers than before due to the scheduling. I will update the testcase. Thanks. From: gcc-patches-ow...@gcc.gnu.org

Fix PR77309, combine eliminates sign bit comparison

In this PR, we manage to simplify the code down to (lt (and (reg) (signbit)) (const 0)) simplify_comparison then calls make_compound_operation on the AND expression, and that turns it into a ZERO_EXTRACT of a single bit, changing the meaning of the comparison. The problem is a special case

[PATCH VECT]Skip unnecessary data dependence check after visited store stmt in slp

Hi, Function vect_slp_analyze_node_dependences delays data-dependence check for visited store stmts until we run into the last store, because all stores are sunk/vectorized at the position of the last one. The problem is that it still checks data-dep for current store stmt after the delay part

Re: [PATCH, GCC] Fix conflicting posix_memalign declaration error

On 28/10/16 11:38, Bernd Schmidt wrote: > On 10/27/2016 10:47 PM, Caroline Tice wrote: >> >> * config/i386/pmm_malloc.h (posix_memalign): Add ifdefs to only >> decorate the declaration with 'throw()' if __GLIBC__ is defined. > > I seem to recall a similar patch being submitted by

Re: [patch] Use straight-line sequence for signed overflow additive operation

On 10/27/2016 05:26 PM, Eric Botcazou wrote: as suggested by Segher, this changes the generic signed-signed-signed case of expand_addsub_overflow to using a straight-line code sequence instead of a branchy one, the new sequence being also shorter. * dojump.c

Re: [PATCH, GCC] Fix conflicting posix_memalign declaration error

On 10/27/2016 10:47 PM, Caroline Tice wrote: * config/i386/pmm_malloc.h (posix_memalign): Add ifdefs to only decorate the declaration with 'throw()' if __GLIBC__ is defined. I seem to recall a similar patch being submitted by Szabolcs. My suggestion at the time was to move

Re: [PATCH] Fix computation of register limit for -fsched-pressure

Forwarding to list as well. From: Tamar Christina Sent: Friday, October 28, 2016 10:52:17 AM To: Pat Haugen; Maxim Kuvyrkov Cc: GCC Patches Subject: Re: [PATCH] Fix computation of register limit for -fsched-pressure Hi Pat, The commit seems to be causing

Re: [PATCH, ARM/testsuite 6/7] Force soft float in ARMv6-M and ARMv8-M Baseline options

On 22/09/16 16:47, Richard Earnshaw (lists) wrote: On 22/09/16 15:51, Thomas Preudhomme wrote: Sorry, noticed an error in the patch. It was not caught during testing because GCC was built with --with-mode=thumb. Correct patch attached. Best regards, Thomas On 22/09/16 14:49, Thomas

[PATCH][GIMPLE FE] Revert some unnecesary changes, get a .gimple dump

Tested on x86_64-unknown-linux-gnu. Richard. 2016-10-28 Richard Biener c/ * gimple-parser.c: Include tree-dump.h. (c_parser_parse_gimple_body): Do not claim PROP_gimple_lcf or PROP_gimple_leh. Dump to .gimple dump file.

Re: [PATCH] Fix COMPONENT_REF expansion (PR rtl-optimization/77919)

On Fri, Oct 28, 2016 at 10:52:34AM +0200, Richard Biener wrote: > > I've already committed the original patch based on Eric's review, but > > managed to come up with another testcase that still ICEs (one with two > > different complex modes). Is the following ok for trunk if it passes > >

Re: [PATCH] Fix COMPONENT_REF expansion (PR rtl-optimization/77919)

On Fri, 28 Oct 2016, Jakub Jelinek wrote: > On Fri, Oct 28, 2016 at 01:32:22AM -0600, Jeff Law wrote: > > >I think so. I'll leave the rest to people more familiar with RTL > > >expansion -- generally I thought the callers of expand() have to deal > > >with expansions that return a different

Re: [PATCH] Fix COMPONENT_REF expansion (PR rtl-optimization/77919)

On Fri, Oct 28, 2016 at 01:32:22AM -0600, Jeff Law wrote: > >I think so. I'll leave the rest to people more familiar with RTL > >expansion -- generally I thought the callers of expand() have to deal > >with expansions that return a different mode? > You generally have to deal with expansions that

Re: [PR debug/77773] segfault when compiling __simd64_float16_t with -g

On Thu, Oct 27, 2016 at 6:14 PM, Aldy Hernandez wrote: > On 10/27/2016 12:35 AM, Richard Biener wrote: >> >> On Wed, Oct 26, 2016 at 9:17 PM, Aldy Hernandez wrote: >>> >>> The following one-liner segfaults on arm-eabi when compiled with >>> -mfloat-abi=hard

Re: [PATCH] Fix and testcases for pr72747

On Thu, Oct 27, 2016 at 5:37 PM, Will Schmidt wrote: > Hi, > > Per PR72747, A statement such as "v = vec_splats (1);" correctly > initializes a vector. However, a statement such as "v[1] = v[0] = > vec_splats (1);" initializes both v[1] and v[0] to random garbage. > >

Re: [PATCH] Fix host_size_t_cst_p predicate

On Thu, Oct 27, 2016 at 5:06 PM, Martin Liška wrote: > On 10/27/2016 03:35 PM, Richard Biener wrote: >> On Thu, Oct 27, 2016 at 9:41 AM, Martin Liška wrote: >>> Running simple test-case w/o the proper header file causes ICE: >>> strncmp ("a", "b", -1); >>> >>>

[PATCH][GIMPLE FE] Adjust __GIMPLE parsing

The following handles __GIMPLE as declspec which better follows other similar handling. It also reverts the C FE parts back to rely on finish_function (that adjusts things like visibility - sth we'll need in the end). And it makes the __GIMPLE specs (currently only startswith) optional. Tested

Re: [arm.c] Use VAR_P

On 28/10/16 06:00, Prathamesh Kulkarni wrote: Hi, This patch uses replaces TREE_CODE(x) == VAR_DECL by VAR_P(x) in arm.c. Bootstrap+tested on arm-linux-gnueabihf. OK to commit ? Ok (I would consider this obvious). Thanks, Kyrill Thanks, Prathamesh

Re: RFC [2/3] divmod transform v2 - override expand_divmod_libfunc for ARM port

On 27/10/16 14:31, Prathamesh Kulkarni wrote: On 26 October 2016 at 18:51, Kyrill Tkachov wrote: On 16/10/16 07:00, Prathamesh Kulkarni wrote: Hi, This patch overrides expand_divmod_libfunc hook for ARM port. I separated the SImode tests into separate file from

Re: [PATCH] Fix COMPONENT_REF expansion (PR rtl-optimization/77919)

On 10/28/2016 01:25 AM, Richard Biener wrote: On Thu, 27 Oct 2016, Jakub Jelinek wrote: Hi! The following testcase ICEs on x86_64-linux with -O1, the problem is that we expand assignment from COMPONENT_REF of MEM_REF into a V4SImode SSA_NAME. The MEM_REF has non-addressable DCmode var inside

Re: [PATCH] Fix COMPONENT_REF expansion (PR rtl-optimization/77919)

On Thu, 27 Oct 2016, Jakub Jelinek wrote: > Hi! > > The following testcase ICEs on x86_64-linux with -O1, the problem is > that we expand assignment from COMPONENT_REF of MEM_REF into a V4SImode > SSA_NAME. The MEM_REF has non-addressable DCmode var inside of it, and > type of a struct

Re: [PATCH] Fix COMPONENT_REF expansion (PR rtl-optimization/77919)

> Though, perhaps COMPLEX_MODE_P (mode1) is also wrong, if mode1 isn't > GET_MODE (op0), then we still will return something with unexpected mode > (e.g. DCmode vs. CDImode); I wonder if for such mismatches we shouldn't > just force_reg (convert_modes ()) each CONCAT operand separately and >

Re: [PATCH] Fix a REE bug (PR rtl-optimization/78132)

> 2016-10-27 Jakub Jelinek > > PR rtl-optimization/78132 > * ree.c (combine_reaching_defs): Give up if copy_needed and > !HARD_REGNO_MODE_OK (REGNO (src_reg), dst_mode). > > * gcc.target/i386/pr78132.c: New test. OK, thanks. -- Eric Botcazou