[RFC] gcc lto&binutils: Load different gcc's bfd-plugin automatically

2019-03-05 Thread JunMa
Hi All We are now optimizing some projects with lto enabled, however, there are some issues. First, lto_plugin.so needs to be passed to ar/nm/ranlib. For example, build static library with lto: gcc -flto -O2 a.c -c -o a.o gcc -flto -O2 b.c -c -o b.o ar rcs --plugin=/path/to/lto_plugin.so   libx.

Re: A bug in vrp_meet?

2019-03-05 Thread Richard Biener
On Mon, Mar 4, 2019 at 11:01 PM Qing Zhao wrote: > > Hi, Richard, > > > On Mar 4, 2019, at 5:45 AM, Richard Biener > > wrote: > >> > >> It looks like DOM fails to visit stmts generated by simplification. Can > >> you open a bug report with a testcase? > >> > >> > >> The problem is, It took me q

Re: [RFC] gcc lto&binutils: Load different gcc's bfd-plugin automatically

2019-03-05 Thread Richard Biener
On Tue, Mar 5, 2019 at 10:41 AM JunMa wrote: > > Hi All > > We are now optimizing some projects with lto enabled, however, > there are some issues. > First, lto_plugin.so needs to be passed to ar/nm/ranlib. > For example, build static library with lto: > > gcc -flto -O2 a.c -c -o a.o > gcc -flto -

Re: A bug in vrp_meet?

2019-03-05 Thread Richard Biener
On Tue, Mar 5, 2019 at 10:48 AM Richard Biener wrote: > > On Mon, Mar 4, 2019 at 11:01 PM Qing Zhao wrote: > > > > Hi, Richard, > > > > > On Mar 4, 2019, at 5:45 AM, Richard Biener > > > wrote: > > >> > > >> It looks like DOM fails to visit stmts generated by simplification. Can > > >> you ope

Re: [RFC] gcc lto&binutils: Load different gcc's bfd-plugin automatically

2019-03-05 Thread JunMa
在 2019/3/5 下午5:55, Richard Biener 写道: On Tue, Mar 5, 2019 at 10:41 AM JunMa wrote: Hi All We are now optimizing some projects with lto enabled, however, there are some issues. First, lto_plugin.so needs to be passed to ar/nm/ranlib. For example, build static library with lto: gcc -flto -O2

Re: A bug in vrp_meet?

2019-03-05 Thread Richard Biener
On Tue, Mar 5, 2019 at 11:44 AM Richard Biener wrote: > > On Tue, Mar 5, 2019 at 10:48 AM Richard Biener > wrote: > > > > On Mon, Mar 4, 2019 at 11:01 PM Qing Zhao wrote: > > > > > > Hi, Richard, > > > > > > > On Mar 4, 2019, at 5:45 AM, Richard Biener > > > > wrote: > > > >> > > > >> It looks

Re: GSoC Project Ideas

2019-03-05 Thread Eric Gallager
On 3/3/19, Patrick Palka wrote: > Hi everyone, > > I am very interested in working on GCC as part of GSoC this year. A few > years > ago I was a somewhat active code contributor[1] and unfortunately my > contributing waned once I went back to school, but I'm excited to > potentially > have the op

Re: [RFC] gcc lto&binutils: Load different gcc's bfd-plugin automatically

2019-03-05 Thread Joseph Myers
On Tue, 5 Mar 2019, Richard Biener wrote: > Well, why not go a step further and add a bfd-plugin note that suggests > the plugin to be used if it is installed? That could contain for example > lto_plugin_gcc8.so (to be installed in /lib/bfd-plugins/). Alternatively > a full path could be specifi

Re: About BZ#87210 [RFE] To initialize automatic stack variables

2019-03-05 Thread Segher Boessenkool
Hi! On Mon, Mar 04, 2019 at 09:45:37PM +0100, David Brown wrote: > Forcing "stolen_key" to be zero initialised does not help anyone - > options for that just make code slower and hide errors that would occur > with other compiler options. The challenge is to make sure /key/ is > zeroed out aft

Re: About BZ#87210 [RFE] To initialize automatic stack variables

2019-03-05 Thread David Brown
On 05/03/2019 19:37, Segher Boessenkool wrote: Hi! On Mon, Mar 04, 2019 at 09:45:37PM +0100, David Brown wrote: Forcing "stolen_key" to be zero initialised does not help anyone - options for that just make code slower and hide errors that would occur with other compiler options. The challen

Re: A bug in vrp_meet?

2019-03-05 Thread Jeff Law
On 3/1/19 10:49 AM, Qing Zhao wrote: > Jeff, > > thanks a lot for the reply. > > this is really helpful. > > I double checked the dumped intermediate file for pass “dom3", and > located the following for _152: > > BEFORE the pass “dom3”, there is no _152, the corresponding Block > looks lik

Re: About BZ#87210 [RFE] To initialize automatic stack variables

2019-03-05 Thread Martin Sebor
On 3/5/19 1:36 PM, David Brown wrote: On 05/03/2019 19:37, Segher Boessenkool wrote: Hi! On Mon, Mar 04, 2019 at 09:45:37PM +0100, David Brown wrote: Forcing "stolen_key" to be zero initialised does not help anyone - options for that just make code slower and hide errors that would occur wit

Re: A bug in vrp_meet?

2019-03-05 Thread Jeff Law
On 3/4/19 4:45 AM, Richard Biener wrote: > On Fri, Mar 1, 2019 at 10:02 PM Qing Zhao wrote: >> >> >> On Mar 1, 2019, at 1:25 PM, Richard Biener >> wrote: >> >> On March 1, 2019 6:49:20 PM GMT+01:00, Qing Zhao >> wrote: >> >> Jeff, >> >> thanks a lot for the reply. >> >> this is really helpful.

Re: A bug in vrp_meet?

2019-03-05 Thread Jeff Law
On 3/5/19 7:44 AM, Richard Biener wrote: > So fixing it properly with also re-optimize_stmt those stmts so we'd CSE > the MAX_EXPR introduced by folding makes it somewhat ugly. > > Bootstrapped on x86_64-unknown-linux-gnu, testing in progress. > > Any ideas how to make it less so? I can split o

Re: About BZ#87210 [RFE] To initialize automatic stack variables

2019-03-05 Thread Mark Wielaard
On Tue, Mar 05, 2019 at 02:17:51PM -0700, Martin Sebor wrote: > The SECURE project adds the function attribute stack_erase that > serves the purpose described above. It works on stack frames by > design rather than applying to individual stack objects. > The presentation they delivered at Cauldron

Re: About BZ#87210 [RFE] To initialize automatic stack variables

2019-03-05 Thread Segher Boessenkool
On Tue, Mar 05, 2019 at 09:36:56PM +0100, David Brown wrote: > On 05/03/2019 19:37, Segher Boessenkool wrote: > >On Mon, Mar 04, 2019 at 09:45:37PM +0100, David Brown wrote: > >>void foo(void) { > >> char key[20]; > >> strcpy(key, "Top secret"); > >> usekey(key); > >> memset(key, 0,

Thank you!

2019-03-05 Thread SaapVer
Hi DannyEdupt, Thank you for contacting us. We will be in touch with you shortly. -- This e-mail was sent from a contact form on SaapVer (http://saapver.com/)