Emit a variable defined in gcc

2020-06-29 Thread Harshit Sharma via Gcc
Hello, I am working on a gcc patch for asan. The patch is almost ready except one thing. To make sure that the user has applied this patch before using asan feature, I want to declare an additional variable in gcc which is reference by our source code so that if this patch is missing, the user gets

RE: design automation professionals

2020-06-29 Thread Emery White
Hi, Did you had a chance to review my previous mail which I sent across regarding cybersecurity and IT risk management professionals? If you are interested please drop me a note so that we can connect and discuss about the opportunity. Cheers! Regards, Emery White *From:* Emery Whit

Re: RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Joseph Myers
On Mon, 29 Jun 2020, Erick Ochoa wrote: > We are not targeting C++ at the moment. What contexts exist in C where we > require constant expressions? On the top of my head I have array sizes and > initialization of static variables? In such cases, then yes we agree that we Bit-field widths, static

Re: RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Martin Jambor
Hi, On Mon, Jun 29 2020, Erick Ochoa wrote: > On 29.06.20 06:05, Martin Jambor wrote: >> Hi, >> >> On Mon, Jun 29 2020, Erick Ochoa wrote: >>> == How do we get what we want? == >>> >>> Ideally what we want is to: >>> >> >> [...] >> >>> * Disable constant propagation and other optimizations: >>>

Re: RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Erick Ochoa
On 29.06.20 06:05, Martin Jambor wrote: Hi, On Mon, Jun 29 2020, Erick Ochoa wrote: == How do we get what we want? == Ideally what we want is to: [...] * Disable constant propagation and other optimizations: * possibly __attribute__((noipa)) [...] == What's the WORST CASE perfo

Re: RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Martin Jambor
Hi, On Mon, Jun 29 2020, Erick Ochoa wrote: > == How do we get what we want? == > > Ideally what we want is to: > [...] > * Disable constant propagation and other optimizations: >* possibly __attribute__((noipa)) [...] > == What's the WORST CASE performance of having an unknown sizeof? ==

Re: RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Erick Ochoa
On 29.06.20 04:08, Richard Biener wrote: On Mon, Jun 29, 2020 at 1:05 PM Richard Biener wrote: On Mon, Jun 29, 2020 at 11:56 AM Erick Ochoa wrote: Hello, I have been working on link time optimization for C that may change the size of structs (at link time). We are close to sharing the r

Re: RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Erick Ochoa
On 29.06.20 04:05, Richard Biener wrote: On Mon, Jun 29, 2020 at 11:56 AM Erick Ochoa wrote: Hello, I have been working on link time optimization for C that may change the size of structs (at link time). We are close to sharing the results we have so far, but there are a couple of missing

Re: Customized coverage instrumentation for multiple C files

2020-06-29 Thread Martin Liška
On 6/27/20 5:33 AM, Shuai Wang via Gcc wrote: virtual unsigned int execute(function *fun) override which has no idea about the .C file information. In LLVM all .C files are roughly maintained in separate "modules" but I just don't know how to access such information in GIMPLE. Hey. Please tak

Re: Automatically generated ChangeLog files - script

2020-06-29 Thread Martin Liška
@Alexander: May I please remind you this? Martin On 6/24/20 10:28 AM, Martin Liška wrote: On 6/22/20 3:15 PM, Alexandre Oliva wrote: On May 26, 2020, Martin Liška wrote: On 5/26/20 12:15 PM, Pierre-Marie de Rodat wrote: * contracts.adb, einfo.adb, exp_ch9.adb, sem_ch12.adb, It'

Re: RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Jakub Jelinek via Gcc
On Mon, Jun 29, 2020 at 01:05:20PM +0200, Richard Biener via Gcc wrote: > > // source code > > struct astruct a; > > memset(a, 0, sizeof(a)); > > > > // parse time > > memset(a, 0, 64); Actually, I don't see the point at all, it doesn't matter if the user used sizeof(a) or 64 knowing that the stru

Re: RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Richard Biener via Gcc
On Mon, Jun 29, 2020 at 1:05 PM Richard Biener wrote: > > On Mon, Jun 29, 2020 at 11:56 AM Erick Ochoa > wrote: > > > > Hello, > > > > I have been working on link time optimization for C that may change the > > size of structs (at link time). We are close to sharing the results we > > have so far

Re: RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Richard Biener via Gcc
On Mon, Jun 29, 2020 at 11:56 AM Erick Ochoa wrote: > > Hello, > > I have been working on link time optimization for C that may change the > size of structs (at link time). We are close to sharing the results we > have so far, but there are a couple of missing pieces left to work on: > > Implement

GCC 10.1.1 Status Report (2020-06-29)

2020-06-29 Thread Richard Biener
Status == The GCC 10 branch is in regression and documentation fixing mode. We're close to two months after the GCC 10.1 release which means a first bugfix release is about to happen. The plan is to release mid July and I am targeting for a release candidate mid next week, no later than Ju

RFC noipa sizeof function for record relayout at link time

2020-06-29 Thread Erick Ochoa
Hello, I have been working on link time optimization for C that may change the size of structs (at link time). We are close to sharing the results we have so far, but there are a couple of missing pieces left to work on: Implementations of sizeof and offsetof that support this change in stru

Re: TLS Implementation Across Architectures

2020-06-29 Thread Alexandre Oliva
On Jun 25, 2020, Joel Sherrill wrote: > Is there some documentation on how it is implemented on architectures not > in Ulrich's paper? Uli's paper pre-dates GNU2 TLS, I'm not sure whether he updated it to cover it, so https://www.fsfla.org/~lxoliva/writeups/TLS/ might be useful. -- Alexandre O