[PATCH, PR86257, i386/debug] Fix insn prefix in tls_global_dynamic_64_

Hi, [ The analysis of this PR was done at https://stackoverflow.com/a/33557963 , November 2015. ] This tls sequence: ... 0x00 .byte 0x66 0x01 leaq x@tlsgd(%rip),%rdi 0x08 .word 0x 0x0a rex64 0x0b call __tls_get_addr@plt ... starts with an insn prefix, produced using a .byte. When using a .l

Make LABLE_DECLs mostly non-indexable

Hi, while looking on the stats of types of nodes streamed into global stream I notied that we stream all label decls globally. This is quite obvious omision and we need to keep indexable only those that can cross function boundary. While doing so i also noticed special handling of IMPORTED_DECL

[gomp,doc] Move www.openmp.org from http to https

I'm wondering whether we really need all those links instead of just using a textual reference? This can become (and has in this case) a bit of a maintenance challenge. For now I applied the patch below, but perhaps we can simplify this still? Gerald 2018-06-24 Gerald Pfeifer * libg

Re: [PATCH] Avoid changing DR for scatter/gather refs

> 2018-06-21 Richard Biener > > * tree-data-ref.c (dr_step_indicator): Handle NULL DR_STEP. > * tree-vect-data-refs.c (vect_analyze_possibly_independent_ddr): > Avoid calling vect_mark_for_runtime_alias_test with gathers or scatters. > (vect_analyze_data_ref_dependence):

[PATCH] specify large command line option arguments (PR 82063)

Storing integer command line option arguments in type int limits options such as -Wlarger-than= or -Walloca-larger-than to at most INT_MAX (see bug 71905). Larger values wrap around zero. The value zero is considered to disable the option, making it impossible to specify a zero limit. To get ar

Re: [patch] add -nolibc option

> On 22 Jun 2018, at 22:39, Jeff Law wrote: >> +@item -nolibc >> +@opindex nolibc >> +Do not use the C library or system libraries tightly couple with it when > s/tightly couple/ that tightly couple/ > > or > > s/couple/coupled/ > > OK with either of those trivial fixes. Great, Thanks Jeff

Re: [PATCH, PR86257, i386/debug] Fix insn prefix in tls_global_dynamic_64_

> Hi, > > [ The analysis of this PR was done at https://stackoverflow.com/a/33557963 , > November 2015. ] > > This tls sequence: > ... > 0x00 .byte 0x66 > 0x01 leaq x@tlsgd(%rip),%rdi > 0x08 .word 0x > 0x0a rex64 > 0x0b call __tls_get_addr@plt > ... > starts with an insn prefix, produced usi

Re: [PATCH, PR86257, i386/debug] Fix insn prefix in tls_global_dynamic_64_

Hi, searching for other occurences I see: jan@skylake:~/trunk/gcc/config/i386> grep ASM_BYTE *md *.c i386.md:return ASM_BYTE "0x9e"; i386.md:fputs (ASM_BYTE "0x66\n", asm_out_file); i386.md:fputs (ASM_BYTE "0x66\n", asm_out_file); i386.c: fputs (ASM_BYTE "0x48, 0x8d, 0xa4, 0x24, 0x00,

Re: [PATCH 1/2] Untangle stddef.h a little

On Tue, 19 Jun 2018, Joseph Myers wrote: > These two patches are OK, please commit. I created ChangeLog entries and committed both patches (one a few days ago, the second just now). Thank you, Maya! If you have any further clean-ups, I'll be happy to help by committing them (once approved). >

Re: [PRs fortran/82972, fortran/83088, fortran/85851] Fix ICE with -finit-derived when using iso_c_binding

Thanks for the review. I will commit tomorrow. --- Fritz Reese On Sat, Jun 23, 2018 at 11:57 AM, Steve Kargl wrote: > On Fri, Jun 22, 2018 at 04:46:19PM -0400, Fritz Reese wrote: >> >> In any case, the changelog is here, and the patch is attached. Aside >> from the issues mentioned below the com

Re: [PATCH 0/3][POPCOUNT]

On Fri, Jun 22, 2018 at 5:11 PM, Kugan Vivekanandarajah wrote: > When we set niter with maybe_zero, currently final_value_relacement > will not happen due to expression_expensive_p not handling. Patch 1 > adds this. > > With that we have the following optimized gimple. > >[local count: 1181116

Re: [PATCH 0/3][POPCOUNT]

Hi Jeff, Thanks for the comments. On 23 June 2018 at 02:06, Jeff Law wrote: > On 06/22/2018 03:11 AM, Kugan Vivekanandarajah wrote: >> When we set niter with maybe_zero, currently final_value_relacement >> will not happen due to expression_expensive_p not handling. Patch 1 >> adds this. >> >> Wi

Re: [PATCH 0/3][POPCOUNT]

Hi Bin, Thanks for your comments. On 25 June 2018 at 11:15, Bin.Cheng wrote: > On Fri, Jun 22, 2018 at 5:11 PM, Kugan Vivekanandarajah > wrote: >> When we set niter with maybe_zero, currently final_value_relacement >> will not happen due to expression_expensive_p not handling. Patch 1 >> adds t

Re: [PATCH 0/3][POPCOUNT]

On Mon, Jun 25, 2018 at 11:37 AM, Kugan Vivekanandarajah wrote: > Hi Bin, > > Thanks for your comments. > > On 25 June 2018 at 11:15, Bin.Cheng wrote: >> On Fri, Jun 22, 2018 at 5:11 PM, Kugan Vivekanandarajah >> wrote: >>> When we set niter with maybe_zero, currently final_value_relacement >>>

Re: [PATCH 0/3][POPCOUNT]

Hi Bin, On 25 June 2018 at 13:56, Bin.Cheng wrote: > On Mon, Jun 25, 2018 at 11:37 AM, Kugan Vivekanandarajah > wrote: >> Hi Bin, >> >> Thanks for your comments. >> >> On 25 June 2018 at 11:15, Bin.Cheng wrote: >>> On Fri, Jun 22, 2018 at 5:11 PM, Kugan Vivekanandarajah >>> wrote: When we