Support for named address spaces in C++

Hi all, I’ve added a named address space to our backend and I noticed that it is only support in C. Has anyone had experience porting this feature to C++? Is there any technical reason why it’s not supported? Thank you, Max

Re: Support for named address spaces in C++

On Wed, Jun 3, 2020 at 2:32 PM Max Ruttenberg via Gcc wrote: > > Hi all, > > I’ve added a named address space to our backend and I noticed that it is only > support in C. > Has anyone had experience porting this feature to C++? Is there any technical > reason why it’s not

Re: [PATCH 5/5] gcc-plugins/stackleak: Don't instrument vgettimeofday.c in arm64 VDSO

On Thu, Jun 04, 2020 at 04:49:57PM +0300, Alexander Popov wrote: > Don't try instrumenting functions in arch/arm64/kernel/vdso/vgettimeofday.c. > Otherwise that can cause issues if the cleanup pass of stackleak gcc plugin > is disabled. > > Signed-off-by: Alexander Popov

Re: [PATCH 1/5] gcc-plugins/stackleak: Exclude alloca() from the instrumentation logic

On Thu, Jun 4, 2020 at 3:51 PM Alexander Popov wrote: > Some time ago Variable Length Arrays (VLA) were removed from the kernel. > The kernel is built with '-Wvla'. Let's exclude alloca() from the > instrumentation logic and make it simpler. The build-time assertion > against alloca() is added ins

Re: [PATCH 5/5] gcc-plugins/stackleak: Don't instrument vgettimeofday.c in arm64 VDSO

On Thu, Jun 4, 2020 at 3:58 PM Will Deacon wrote: > On Thu, Jun 04, 2020 at 04:49:57PM +0300, Alexander Popov wrote: > > Don't try instrumenting functions in arch/arm64/kernel/vdso/vgettimeofday.c. > > Otherwise that can cause issues if the cleanup pass of stackleak gcc pl

Re: [PATCH 5/5] gcc-plugins/stackleak: Don't instrument vgettimeofday.c in arm64 VDSO

On Thu, Jun 4, 2020 at 4:21 PM Alexander Popov wrote: > On 04.06.2020 17:14, Jann Horn wrote: > > Maybe at some point we should replace exclusions based on > > GCC_PLUGINS_CFLAGS and KASAN_SANITIZE and UBSAN_SANITIZE and > > OBJECT_FILES_NON_STANDARD and so on with something more generic... > > so

Re: [PATCH 2/5] gcc-plugins/stackleak: Use asm instrumentation to avoid useless register saving

registers__ 0 > #endif Nit: if you do another version, please move it before `noclone` to keep the order (`fallthrough` was added in the wrong place). Otherwise don't worry, I will sort it together with `fallthrough` when I send a patch. > +/* > + * Optional: only supported since

Question about comparing function function decls

I'm trying to determine during LTO optimization (with one partition) whether of not a function call is to a function in the partition. Here is the routine I've written. Note, I'm willing to admit up front that the comparison below ( ) is probably dicey. ---

Re: [PATCH 0/5] Improvements of the stackleak gcc plugin

On Thu, Jun 04, 2020 at 04:49:52PM +0300, Alexander Popov wrote: > In this patch series I collected various improvements of the stackleak > gcc plugin. Great; thank you! I'll take a closer look at this shortly! -- Kees Cook

help with uninstalling gcc

Hi,I've installed gcc 8, how can I uninstall it? RegardsDiego Pardo

Re: Question about comparing function function decls

On Thu, Jun 4, 2020 at 10:24 PM Gary Oblock via Gcc wrote: > > > > > > I'm trying to determine during LTO optimization (with one partition) > whether of not a function call is to a function in the partition. > > Here is the routine

Re: gcc math functions for OpenMP vectoization

On Fri, Jun 05, 2020 at 01:58:55PM +, Feltgen, Eric wrote: > my name is Eric, I'm a german student at RWTH Aachen University currently > researching OpenMP. > > > For my research, I'm also looking at math functions provided by compilers > like GCC. When writ

Re: help with uninstalling gcc

On Fri, 5 Jun 2020 at 10:12, Diego Pardo via Gcc wrote: > > Hi,I've installed gcc 8, how can I uninstall it? That depends how you installed it, and you've told us nothing useful that would allow us to help you. But in any case, please direct this question to the gcc-h...@gcc.gn

Re: gcc math functions for OpenMP vectoization

On June 5, 2020 7:58:20 PM GMT+02:00, Toon Moene wrote: >On 6/5/20 6:10 PM, Tobias Burnus wrote: > >> On 6/5/20 4:11 PM, Jakub Jelinek via Gcc wrote: > >>> It is glibc that provides them, not GCC. >>> See >>> >https://sourceware.org/git/?p=glibc.git;

Re: gcc math functions for OpenMP vectoization

On Fri, 5 Jun 2020 at 18:59, Toon Moene wrote: > > On 6/5/20 6:10 PM, Tobias Burnus wrote: > > > On 6/5/20 4:11 PM, Jakub Jelinek via Gcc wrote: > > >> It is glibc that provides them, not GCC. > >> See > >> https://sourceware.org/git/?p=glibc.git;

Re: AArch64 failures on tester

On Fri, 2020-06-05 at 14:27 +, Alex Coplan wrote: > Hello, > > Recently Jeff's tester picked up some test failures on AArch64. These > are now fixed as of commit ab563903 but the aarch64-linux-gnu build is > still failing with the following output: > > Old tests that failed, that have disap

Re: GSoC: OMPD conversation

On Fri, Jun 05, 2020 at 03:13:42PM -0400, y2s1982 . wrote: > > > The LLVM's repository for OMPD development is at this github repo > > > , > > > under the branch ompd-test. > > > The OMPD documentation > > >

Re: Max Filippov appointed Xtensa maintainer

On Fri, Jun 5, 2020 at 5:50 PM David Edelsohn wrote: > I am pleased to announce that the GCC Steering Committee has > appointed Max Filippov as Xtensa maintainer. Thank you for your trust. > Please join me in congratulating Max on his new role. > Max, please update

Re: install location of math-vector-fortran.h

* Matthias Klose: > [not subscribed to the libc-alpha list] > > GCC and glibc need to agree on the install location for math-vector-fortran.h. > Currently it is installed into > > /usr/include/finclude/math-vector-fortran.h > > However the file is architecture specifi

Re: install location of math-vector-fortran.h

* Matthias Klose: > this file currently only has lines like: > > !GCC$ builtin (cos) attributes simd (notinbranch) if('x86_64') > > so it shouldn't have any effect to other architectures? Or are the > conditionals explicitly done to exclude the 32bit x86 con

Re: install location of math-vector-fortran.h

On Mon, Jun 08, 2020 at 12:52:36PM +0200, Matthias Klose wrote: > GCC and glibc need to agree on the install location for math-vector-fortran.h. > Currently it is installed into > > /usr/include/finclude/math-vector-fortran.h > > However the file is architecture specific, cur

Inquire a potential bug when printing out GIMPLE ASAN statements

[argc + 12]; // an ASan check, namely, ASAN_MARK, will be inserted at this point } And I am using the following code snippet (basically derived from this post <https://stackoverflow.com/questions/29346772/print-called-function-name-using-gcc-plugin>) to print out all function calls, inc

Re: Inquire a potential bug when printing out GIMPLE ASAN statements

On Tue, Jun 9, 2020 at 3:38 AM Shuai Wang via Gcc wrote: > > Hello! > > I am writing to report a potential bug I encountered when playing with the > GIMPLE IR. I enabled the ASan and would like to print out all ASAN_MARK > statements for the following simple code: > >

Re: Inquire a potential bug when printing out GIMPLE ASAN statements

, Shuai On Tue, Jun 9, 2020 at 3:48 PM Richard Biener wrote: > On Tue, Jun 9, 2020 at 3:38 AM Shuai Wang via Gcc wrote: > > > > Hello! > > > > I am writing to report a potential bug I encountered when playing with > the > > GIMPLE IR. I enabled the ASan and w

Re: Seeking clarification and way forward on limited scope variables.

intf("%d\n",Local); > 9 } > 10 > 11 return 0; > 12 } > -------- > When compiled in debug mode with compilers including (trunk gcc and trunk > clang) and debugging with GDB at Line No.6, the following behavior is observed > Breakpoint 1, main (Argc=1, Argv=0x

Re: Inquire a potential bug when printing out GIMPLE ASAN statements

ance that I can still pinpoint this special > function call? Currently I can iterate all GIMPLE call statements, but how > to exactly figure out ASAN_MARK seems quite obscure. > > Thank you! > > Best, > Shuai > > On Tue, Jun 9, 2020 at 3:48 PM Richard Biener > w

Re: Inquire a potential bug when printing out GIMPLE ASAN statements

can iterate all GIMPLE call statements, but how >> to exactly figure out ASAN_MARK seems quite obscure. >> >> Thank you! >> >> Best, >> Shuai >> >> On Tue, Jun 9, 2020 at 3:48 PM Richard Biener >> wrote: >> >>> On Tue, Jun 9, 2020 at 3:38

Ideal Lifestyles you must Know: Finding happiness in relationship

[image: Ideal LIfestyles] Our Latest Posts Relationship matters: be whom you are BE WHOM YOU ARE Relationship gives humanity a chance to fellowship with each other in harmony. In fact, the essence of marriage is to fellowship together harnessing every potential deposits in both partners. True frie

Re: 4.2 source

rhel was not done for > 32bit. > > Thanks, > Jim Dugan GCC 4.2 sources? Sure, in the releases area you can find that release and many others going back much further into ancient history. https://gcc.gnu.org/releases.html paul

Re: [PATCH 1/5] gcc-plugins/stackleak: Exclude alloca() from the instrumentation logic

On Thu, Jun 04, 2020 at 06:23:38PM +0300, Alexander Popov wrote: > On 04.06.2020 17:01, Jann Horn wrote: > > On Thu, Jun 4, 2020 at 3:51 PM Alexander Popov wrote: > >> Some time ago Variable Length Arrays (VLA) were removed from the kernel. > >> The kernel is built with '-Wvla'. Let's exclude allo

Re: [PATCH 3/5] gcc-plugins/stackleak: Add 'verbose' plugin parameter

On Thu, Jun 04, 2020 at 04:49:55PM +0300, Alexander Popov wrote: > Add 'verbose' plugin parameter for stackleak gcc plugin. > It can be used for printing additional info about the kernel code > instrumentation. > > For using it add the following to scripts/Makefile.gc

Re: [PATCH 2/5] gcc-plugins/stackleak: Use asm instrumentation to avoid useless register saving

lable for x86_64 and i386 starting from gcc-7. > > 2. Insert calling stackleak_track_stack() in asm: > asm volatile("call stackleak_track_stack" :: "r" (current_stack_pointer)) > Here we use ASM_CALL_CONSTRAINT trick from arch/x86/include/asm/asm.h. > The i

Re: [PATCH 4/5] gcc-plugins/stackleak: Don't instrument itself

On Thu, Jun 04, 2020 at 04:49:56PM +0300, Alexander Popov wrote: > There is no need to try instrumenting functions in kernel/stackleak.c. > Otherwise that can cause issues if the cleanup pass of stackleak gcc plugin > is disabled. > > Signed-off-by: Alexander Popov Acke

Re: [PATCH 5/5] gcc-plugins/stackleak: Don't instrument vgettimeofday.c in arm64 VDSO

On Thu, Jun 04, 2020 at 02:58:06PM +0100, Will Deacon wrote: > On Thu, Jun 04, 2020 at 04:49:57PM +0300, Alexander Popov wrote: > > Don't try instrumenting functions in arch/arm64/kernel/vdso/vgettimeofday.c. > > Otherwise that can cause issues if the cleanup pass of stackle

Re: [PATCH 0/5] Improvements of the stackleak gcc plugin

On Thu, Jun 04, 2020 at 04:49:52PM +0300, Alexander Popov wrote: > In this patch series I collected various improvements of the stackleak > gcc plugin. Thanks! > Alexander Popov (5): > gcc-plugins/stackleak: Exclude alloca() from the instrumentation logic > gcc-plugins/sta

Re: [IMPORTANT] ChangeLog related changes

> > ChangeLog' which mirrors the error for the opposite condition, > > 'changed file not mentioned in a ChangeLog'). > > I welcome this. > > > > > I've also moved line numbers to the start of the line (like GCC's own > > diagnostics) and

Re: [haifa-sched][restore_pattern] Can we recalculate INSN_TICK for the dependence type of REG_DEP_CONTROL？

On Thu, 2020-04-23 at 10:40 +, xuemaosheng wrote: > Product: GCC > Component: rtl-optimization > Version: 7.3.0 > > > If we add the flag DO_PREDICATION in scheduling ebb, the compiler will try to > predicate the insn when the producer insn has been issued, > and pu

Hello gcc. Why -fvtable-gc was removed from the compiler?

What’s wrong with eliminating unused virtual functions in the binary? Sent from Mail for Windows 10

Re: Hello gcc. Why -fvtable-gc was removed from the compiler?

On Tue, 2020-06-09 at 20:35 +, sotrdg sotrdg via Gcc wrote: > What’s wrong with eliminating unused virtual functions in the binary? Nothing inherently wrong with the concept. But the implementation left a lot to be desired and I think it was ultimately scrapped as unmaintainable. jeff

Re: dejagnu version update?

Maciej W. Rozycki wrote: On Tue, 26 May 2020, Rob Savoye wrote: I'll run some RISC-V remote GCC/GDB testing and compare results for DejaGnu 1.6/1.6.1 vs trunk. It will take several days though, as it takes many hours to go through these testsuite runs. That'd be

Re: dejagnu version update? [CORRECTION: not a regression in DejaGnu; GDB testsuite bug]

Jacob Bachmeyer wrote: Maciej W. Rozycki wrote: [...] I ran a quick bisection and the culprit turned out to be: ba60272a5ac6f6a7012acca03f596a6ed003f044 is the first bad commit commit ba60272a5ac6f6a7012acca03f596a6ed003f044 Author: Jacob Bachmeyer Date: Mon May 25 08:40:46 2020 -0600

Re: [PATCH 5/5] gcc-plugins/stackleak: Don't instrument vgettimeofday.c in arm64 VDSO

vgettimeofday.c. > > > Otherwise that can cause issues if the cleanup pass of stackleak gcc > > > plugin > > > is disabled. > > > > > > Signed-off-by: Alexander Popov > > > --- > > > arch/arm64/kernel/vdso/Makefile | 3 ++- > &g

Re: [IMPORTANT] ChangeLog related changes

On Wed, Jun 10, 2020 at 01:34:54PM +, Tamar Christina wrote: > Hi All, > > We've been wondering since we no longer list authors in the changelog (at > least mklog doesn't generate it), > How do we handle multi author patches nowadays? > > Tried searching for it on the website but couldn’t fi

Re: Automatic vs. manual 'ChangeLog' files updates for devel/ branches etc. (was: [PATCH] wwwdocs: Document devel/omp/gcc-10 branch)

mechanism in > place to make sure that actual GCC tarball etc. releases do have complete > 'ChangeLog' files state. Martin has provided a way to generate patches for all the standard branches instead of checking them in. I think it would be really much better to have a way to ask e

Re: [PATCH 2/5] gcc-plugins/stackleak: Use asm instrumentation to avoid useless register saving

On Wed, Jun 10, 2020 at 06:47:14PM +0300, Alexander Popov wrote: > On 09.06.2020 21:46, Kees Cook wrote: > The inline asm statement that is used for instrumentation is arch-specific. > Trying to add > asm volatile("call stackleak_track_stack") > in gcc plugin o

Re: [PATCH 3/5] gcc-plugins/stackleak: Add 'verbose' plugin parameter

On Wed, Jun 10, 2020 at 06:52:10PM +0300, Alexander Popov wrote: > On 09.06.2020 21:47, Kees Cook wrote: > > On Thu, Jun 04, 2020 at 04:49:55PM +0300, Alexander Popov wrote: > >> Add 'verbose' plugin parameter for stackleak gcc plugin. > >> It can be used f

GDB testsuite overrides default_target_compile and breaks

ed ball back up and get those features merged upstream. As it happens there are about 2 users of DejaGnu there, which means any fatal regression would have been easily caught in the course of change verification (and running binutils/GDB and GCC test suites natively is about as easy as it

GCC 10.1.0 HELP

Hello I am a researcher from Jam Petrochemical company. I want to use OpenACC with GCC compiler(FORTRAN language). I read from your documentation that GCC 10.1.0 supports carrizo, fiji and vega (third and fifth generation) AMD GPU for OpenACC parallelization. I am using following AMD GPU: [AMD

Re: GCC 10.1.0 HELP

On Thu, 11 Jun 2020 at 08:43, MAHDI LOTFI via Gcc wrote: > > Hello > I am a researcher from Jam Petrochemical company. I want to use OpenACC > with GCC compiler(FORTRAN language). I read from your documentation that > GCC 10.1.0 supports carrizo, fiji and vega (third and fifth

Re: dejagnu version update?

Hi, On Wed, 27 May 2020 at 03:58, Rob Savoye wrote: > > On 5/26/20 7:20 PM, Maciej W. Rozycki wrote: > > > I'll run some RISC-V remote GCC/GDB testing and compare results for > > DejaGnu 1.6/1.6.1 vs trunk. It will take several days though, as it takes > >

Is it very hard to implement Zero-overhead deterministic exceptions: Throwing values??

http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0709r0.pdf I really want this feature. How, it looks like this requires changes on RTL, gimple and C++ front-end. Is that very hard to implement it? Sent from Mail for Windows 10

Re: GCC 10.1.0 HELP

Thank you very much. On Thu, Jun 11, 2020 at 4:18 PM Andrew Stubbs wrote: > On 11/06/2020 08:40, MAHDI LOTFI via Gcc wrote: > > [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] > > [1002:6900] (rev 81) > > > > I think my GPU is older than fiji an

Write plugin for `sanopt` or `asan0` passes

Hello, I am writing to inquire the procedure (or any tutorial) to write plugins for the `sanopt` pass. Basically I am doing some analysis of ASan/UBSan checks. I use the following command to dump all passes in IR format: gcc -fdump-tree-all -fsanitize=address test.c To me, I think the following

Re: Is it very hard to implement Zero-overhead deterministic exceptions: Throwing values??

sotrdg sotrdg via Gcc writes: > http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0709r0.pdf > > I really want this feature. How, it looks like this requires changes > on RTL, gimple and C++ front-end. Is that very hard to implement it? If you're asking about setjmp/longjm

Re: Is it very hard to implement Zero-overhead deterministic exceptions: Throwing values??

On Sun, Jun 14, 2020 at 2:27 PM Andi Kleen via Gcc wrote: > > sotrdg sotrdg via Gcc writes: > > > http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0709r0.pdf > > > > I really want this feature. How, it looks like this requires changes > > on RTL, gimple and

How to get the data dependency of GIMPLE variables?

Hello, I am trying to analyze the following gimple statements, where the data dependency of _23 is a tree, whose leave nodes are three constant values {13, 4, 14}. Could anyone shed some light on how such a backward traversal can be implemented? Given _22 used in the last assignment, I have no id

Re: How to get the data dependency of GIMPLE variables?

} Sorry for such naive questions.. I actually searched the documents and GIMPLE pretty print for a while but couldn't find such a way of accessing arbitrary numbers of operands... Best, Shuai On Mon, Jun 15, 2020 at 12:10 PM Marc Glisse wrote: > On Mon, 15 Jun 2020, Shuai Wang via Gcc

Re: Is it very hard to implement Zero-overhead deterministic exceptions: Throwing values??

On Sun, 14 Jun 2020 at 22:34, Andrew Pinski via Gcc wrote: > > On Sun, Jun 14, 2020 at 2:27 PM Andi Kleen via Gcc wrote: > > > > sotrdg sotrdg via Gcc writes: > > > > > http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0709r0.pdf > > > > >

Re: Push to my private branches is disallowed

On June 15, 2020 6:05:26 PM GMT+02:00, Segher Boessenkool wrote: >Hi! > >$ git push -n fsf >To git+ssh://gcc.gnu.org/git/gcc.git > + 1db88c6...71e5e35 cc0 -> refs/users/segher/heads/cc0 (forced update) > >$ git push fsf >Counting objects: 664, done. >Delta compression using up to 64 threads. >Com

SSA_NAME_DEF_STMT or print_gimple_stmt for MEM_REF seems mal-functional

_signal ../../gcc-10.1.0/gcc/toplev.c:328 0x1452134 pp_format(pretty_printer*, text_info*) ../../gcc-10.1.0/gcc/pretty-print.c:1828 0x14533e4 pp_printf(pretty_printer*, char const*, ...) ../../gcc-10.1.0/gcc/pretty-print.c:1773 0x8dcc81 print_gimple_stmt(_IO_FILE*, gimpl

Re: SSA_NAME_DEF_STMT or print_gimple_stmt for MEM_REF seems mal-functional

On June 15, 2020 6:31:38 PM GMT+02:00, Shuai Wang via Gcc wrote: >Hello, > >Suppose given the following SSA statement generated by the `sanopt` >pass: > > _17 = (signed char *) _16; > _18 = *_17; > >I am using the following code to identify that _17 depends on _1

Re: SSA_NAME_DEF_STMT or print_gimple_stmt for MEM_REF seems mal-functional

Thank you very much for your prompt response, Rchard. Sorry I was kinda "learning by doing". I am familiar with LLVM stuff but newbie to GCC specifications. Just want to make sure I got it right; _17 and _16 in the IR code are SSA variables. They are initialized for once and used once.

Re: Push to my private branches is disallowed

fact it *does* seem to allow that, > it's just some "let's send a gazillion emails" script that is > misbehaving. > These are all the reasons why I don't use GCC repo for my personal branches. -- H.J.

Re: Push to my private branches is disallowed

On Mon, Jun 15, 2020 at 2:13 PM Segher Boessenkool wrote: > > On Mon, Jun 15, 2020 at 10:47:48AM -0700, H.J. Lu wrote: > > These are all the reasons why I don't use GCC repo for my personal > > branches. > > Yeah, but I thought a lot of different GCC people might be

Re: Push to my private branches is disallowed

David, The currently implemented rules and automation are not encouraging personal branches in the GCC repository. You are hereby awarded the prize for the understatement of the month.

Re: Push to my private branches is disallowed

ps://github.com/AdaCore/git-hooks/pull/12 is marked "Approved". It >certainly has fixes for some of the issues reported in the GCC context, > >but I'm not sure if it includes a fix for that particular one. And >once >"Approved" has turned into actually pre

Re: SSA_NAME_DEF_STMT or print_gimple_stmt for MEM_REF seems mal-functional

On June 15, 2020 6:58:27 PM GMT+02:00, Shuai Wang wrote: >Thank you very much for your prompt response, Rchard. Sorry I was kinda >"learning by doing". I am familiar with LLVM stuff but newbie to GCC >specifications. > >Just want to make sure I got it right; _17 and _1

Re: SSA_NAME_DEF_STMT or print_gimple_stmt for MEM_REF seems mal-functional

0, Shuai Wang > wrote: > >Thank you very much for your prompt response, Rchard. Sorry I was kinda > >"learning by doing". I am familiar with LLVM stuff but newbie to GCC > >specifications. > > > >Just want to make sure I got it right; _17 and _16 in the IR cod

Re: SSA_NAME_DEF_STMT or print_gimple_stmt for MEM_REF seems mal-functional

M GMT+02:00, Shuai Wang >> wrote: >> >Thank you very much for your prompt response, Rchard. Sorry I was kinda >> >"learning by doing". I am familiar with LLVM stuff but newbie to GCC >> >specifications. >> > >> >Just want to make sure I go

Re: SSA_NAME_DEF_STMT or print_gimple_stmt for MEM_REF seems mal-functional

>>> >Thank you very much for your prompt response, Rchard. Sorry I was kinda >>> >"learning by doing". I am familiar with LLVM stuff but newbie to GCC >>> >specifications. >>> > >>> >Just want to make sure I got it right; _17 and

Re: Push to my private branches is disallowed

e another branch using that name in future, in case somebody pulled the old branch before I deleted it? Randos on the internet aren't going to be basing work on those branches accidentally, they're not fetched by default so you have to make some non-trivial effort to even fetch them. If yo

RFC/RFH - proof of concept for GCC OpenMP 5.0 non-rectangular worksharing-loop implementation

pt to write in C what GCC could roughly emit for it. Note, the test uses (mostly) int types, but in reality it can be other integral types, signed or unsigned, and OpenMP just adds assurances that the loops will not wrap around and otherwise behave well. For both number of iterations computation an

Re-optimize instrumented GIMPLE code

optimization of gcc. However, I just cannot figure out a way of doing so. I use the following command to output the instrumented GIMPLE code: gcc -fdump-tree-all -fplugin=./instrumentor.so -g -fsanitize=address test.c And notice that the instrumented gimple code is right there in the outputs

Use gcov for line coverage info of GIMPLE code

Hello, I am aware of how to use gcov for c code line coverage collection. However, currently I am working on a piece of GIMPLE code (did some instrumentation on the GIMPLE code and therefore is more complex compared to the original C code)l, and would like to collect the line coverage info of GIMP

Re: Use gcov for line coverage info of GIMPLE code

Hello Martin, The issue is that I want to count the coverage of "true/false" branches taken in sanitizer's if conditions.. Best, Shuai On Wed, Jun 17, 2020 at 2:52 PM Martin Liška wrote: > On 6/17/20 5:40 AM, Shuai Wang via Gcc wrote: > > Hello, > > >

Re: Re-optimize instrumented GIMPLE code

nd it (it's somewhat wrapped within .ASAN_CHECK). Best, Shuai On Wed, Jun 17, 2020 at 2:49 PM Martin Liška wrote: > On 6/17/20 4:10 AM, Shuai Wang via Gcc wrote: > > Hello, > > > > Suppose I have changed certain if condition in the GIMPLE code (generated > > by

Re: Re-optimize instrumented GIMPLE code

into always false (done), and hope I can re-launch the dead code elimination pass of GCC to automatically remove that particular sanitizer check (and the if condition). This is just some random hacks, so probably far from the adoption stage... If it does, then i will be glad to reach out and discuss

Re: Re-optimize instrumented GIMPLE code

On Wed, Jun 17, 2020 at 4:11 AM Shuai Wang via Gcc wrote: > > Hello, > > Suppose I have changed certain if condition in the GIMPLE code (generated > by the `sanopt` pass) into the following format: > > if (0 == 1) > { > > } > > Then, in order to c

Re: RFC/RFH - proof of concept for GCC OpenMP 5.0 non-rectangular worksharing-loop implementation

orksharing-loop implementation. Copyright (C) 2020 Free Software Foundation, Inc. GCC is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3, or (at your option) any

Re: Re-optimize instrumented GIMPLE code

On Wed, 2020-06-17 at 15:10 +0800, Shuai Wang via Gcc wrote: > Dear Martin, > > Thanks for the information. I am tentatively experimenting some random > gadgets; given the critical if condition belonging to each sanitizer check, > i will do some data flow analysis and then de

Re: Use gcov for line coverage info of GIMPLE code

Enable coverage-guided fuzzing code instrumentation. Inserts > a call to "__sanitizer_cov_trace_pc" into every basic block. > > And put corresponding builtins to the true/false branches in the > instrumented code. > > Martin > > > > > Best, > > Shuai &

Please put vim swap files into gitignore

Hi, I just found a few unversioned files called .intrinsic.c.swp and similar in my "git status" output. Could somebody please put .*.swp into .gitignore? I'm sure this would save at least 10 reverts :-) Regards Thomas

Re: Please put vim swap files into gitignore

On Thu, 18 Jun 2020 at 19:22, Thomas Koenig via Gcc wrote: > > Hi, > > I just found a few unversioned files called .intrinsic.c.swp and > similar in my "git status" output. > > Could somebody please put .*.swp into .gitignore? I'm sure this > would save at

Re: Please put vim swap files into gitignore

Am 18.06.20 um 20:34 schrieb Jonathan Wakely via Gcc: On Thu, 18 Jun 2020 at 19:22, Thomas Koenig via Gcc wrote: Hi, I just found a few unversioned files called .intrinsic.c.swp and similar in my "git status" output. Could somebody please put .*.swp into .gitignore? I'm

Re: Please put vim swap files into gitignore

On Thu, 18 Jun 2020 at 20:34, Thomas Koenig wrote: > > Am 18.06.20 um 20:34 schrieb Jonathan Wakely via Gcc: > > On Thu, 18 Jun 2020 at 19:22, Thomas Koenig via Gcc wrote: > >> > >> Hi, > >> > >> I just found a few unversioned files called .in

Re: [OMPD] regarding const char **ompd_dll_locations

On Thu, Jun 18, 2020 at 05:24:25PM -0400, y2s1982 . wrote: > (LLVM currently simply puts { "ompd.so", NULL }, but I am assuming this was > just a placeholder.) Let's put there { "libgompd" SONAME_SUFFIX (1), NULL } for now. You'll need to change the SONAME_SUFFIX macros though - remove the ()s aro

Re: [OMPD] regarding const char **ompd_dll_locations

On Thu, Jun 18, 2020 at 06:19:43PM -0400, y2s1982 . wrote: > Thank you for the quick response. I assume, then, there's no need for > making a function to set this global variable at this point. Should I > create a simple unit test that asserts the value to be "libgompd.so.1" for > now, or should I

Publishing paid sponsored post on your site

Hello, We wanted to reach out to you regarding interest in purchasing guest posts on your site octave.org in the form of content that’s linked with the gambling site. Is this something you would be able to offer? And if so, what would your rate be? Looking forward to hearing from you :) Thank

Any implementation of `__sanitizer_cov_trace_basic_block` in GCC?

Hello, I am writing to inquire about the availability of any "__sanitizer_cov_trace_basic_block" implementations in gcc. I somewhat learned from the following mail discussion ( https://gcc.gnu.org/pipermail/gcc-patches/2015-December/437137.html) that `__sanitizer_cov_trace_basic

Exception at "need_ssa_update_p" during GIMPLE instrumentation

fg (flags & TODO_update_ssa_any); else if (flags & TODO_update_ssa_any) update_ssa (flags & TODO_update_ssa_any); gcc_assert (!need_ssa_update_p (fn)); <------ line 1954 of gcc/passes.c for gcc 10.1.0 This really confused me, because when I print out the instrumented GIMP

Re: Exception at "need_ssa_update_p" during GIMPLE instrumentation

OK, I think I know how to solve it. Just return TODO_update_ssa <https://code.woboq.org/gcc/gcc/tree-pass.h.html#249>. On Sun, Jun 21, 2020 at 5:34 PM Shuai Wang wrote: > Hello, > > I am doing instrumentation of GIMPLE code by adding extra coverage > counters at each basic blo

Re: Exception at "need_ssa_update_p" during GIMPLE instrumentation

On June 21, 2020 11:38:49 AM GMT+02:00, Shuai Wang via Gcc wrote: >OK, I think I know how to solve it. Just return TODO_update_ssa ><https://code.woboq.org/gcc/gcc/tree-pass.h.html#249>. If you dump with -vops you'll likely see that virtual operands got out of sync. You ca

await your feedback

Re: [OMPD] API version formatting

On Sat, Jun 20, 2020 at 01:26:59PM -0400, y2s1982 . via Gcc wrote: > I have a question on API version formatting. > I have been looking at the get_api_version() and get_api_version_string() > documentation: > https://www.openmp.org/spec-html/5.0/openmpsu213.html#x269-17920005.5.1.2

Re: [OMPD] API version formatting

On Mon, Jun 22, 2020 at 1:47 PM Jakub Jelinek via Gcc wrote: > > On Sat, Jun 20, 2020 at 01:26:59PM -0400, y2s1982 . via Gcc wrote: > > I have a question on API version formatting. > > I have been looking at the get_api_version() and get_api_version_string() > >

Re: [OMPD] API version formatting

On Mon, Jun 22, 2020 at 03:14:44PM -0400, y2s1982 . via Gcc wrote: > > > If the 4 separate bytes of the version isn't something written somewhere > > in > > > the standard, I'd use something along the lines of > > > #define GCC_VERSION (__GNUC__ * 100

WWDC thread: support for darwin/macOS going forward

there might be some proprietary extensions, so arm-apple-darwin or aarch64-apple-darwin might not work? The next issue would be how exactly to go about adding support for it: Apple had arm-apple-darwin support for gcc in their version of gcc-4.2 that I don't think they ever contributed back ups

Re: WWDC thread: support for darwin/macOS going forward

Hey Eric, Eric Gallager via Gcc wrote: Hi, at Apple's WWDC this year they have announced that they are doing yet another architecture transition, so I was wondering what exactly would be the best way to go about adding support for it? The first issue would be just what to call th

GIMPLE problem

I'm somehow misusing GIMPLE (probably in multiple ways) and I need some help in straightening out this little mess I've made. I'm trying to do the following: In an attempt at structure reorganization (instance interleaving) an array of structures is being transformed into a structure of arrays.

Re: GIMPLE problem

On Wed, Jun 24, 2020 at 1:36 AM Gary Oblock via Gcc wrote: > > I'm somehow misusing GIMPLE (probably in multiple ways) and I need > some help in straightening out this little mess I've made. > > I'm trying to do the following: > > In an attempt at structure r

<    15   16   17   18   19   20   21   22   23   24   >