Re: not computable at load time

2018-05-28 Thread Richard Biener
On Fri, May 25, 2018 at 8:05 PM Paul Koning wrote: > One of my testsuite failures for the pdp11 back end is gcc.c-torture/compile/930326-1.c which is: > struct > { >char a, b, f[3]; > } s; > long i = s.f-&s.b; > It fails with "error: initializer element is not computable at load time". > I

Re: Enabling -ftree-slp-vectorize on -O2/Os

2018-05-28 Thread Richard Biener
On Sat, May 26, 2018 at 12:36 PM Richard Biener wrote: > On May 26, 2018 11:32:29 AM GMT+02:00, Allan Sandfeld Jensen < li...@carewolf.com> wrote: > >I brought this subject up earlier, and was told to suggest it again for > >gcc 9, > >so I have attached the preliminary changes. > > > >My studies

RISC-V problem with weak function references and -mcmodel=medany

2018-05-28 Thread Sebastian Huber
Hello, I try to build a 64-bit RISC-V tool chain for RTEMS. RTEMS doesn't use virtual memory. The reference chips for 64-bit RISC-V such as FU540-C000 locate the RAM at 0x8000_. This forces me to use -mcmodel=medany in 64-bit mode. The ctrbegin.o contains this code (via crtstuff.c): exte

Re: PR80155: Code hoisting and register pressure

2018-05-28 Thread Richard Biener
On Sat, 26 May 2018, Bin.Cheng wrote: > On Fri, May 25, 2018 at 5:54 PM, Richard Biener wrote: > > On May 25, 2018 6:57:13 PM GMT+02:00, Jeff Law wrote: > >>On 05/25/2018 03:49 AM, Bin.Cheng wrote: > >>> On Fri, May 25, 2018 at 10:23 AM, Prathamesh Kulkarni > >>> wrote: > On 23 May 2018 at

Re: Enabling -ftree-slp-vectorize on -O2/Os

2018-05-28 Thread Allan Sandfeld Jensen
On Montag, 28. Mai 2018 12:58:20 CEST Richard Biener wrote: > compile-time effects of the patch on that. Embedded folks may want to rhn > their favorite benchmark and report results as well. > > So I did a -O2 -march=haswell [-ftree-slp-vectorize] SPEC CPU 2006 compile > and run and the compile-ti

Re: not computable at load time

2018-05-28 Thread Andreas Schwab
On Mai 28 2018, Richard Biener wrote: > It means there's no relocation that can express the result of 's.f - &s.b' > and the frontend doesn't consider this a constant expression (likely because > of the conversion). Shouldn't the frontend notice that s.f - &s.b by itself is a constant? Andreas.

Re: not computable at load time

2018-05-28 Thread Richard Biener
On May 28, 2018 12:45:04 PM GMT+02:00, Andreas Schwab wrote: >On Mai 28 2018, Richard Biener wrote: > >> It means there's no relocation that can express the result of 's.f - >&s.b' >> and the frontend doesn't consider this a constant expression (likely >because >> of the conversion). > >Shouldn't

Re: not computable at load time

2018-05-28 Thread Paul Koning
> On May 28, 2018, at 12:03 PM, Richard Biener > wrote: > > On May 28, 2018 12:45:04 PM GMT+02:00, Andreas Schwab wrote: >> On Mai 28 2018, Richard Biener wrote: >> >>> It means there's no relocation that can express the result of 's.f - >> &s.b' >>> and the frontend doesn't consider this

Connect with me on LinkedIn to be on my safe supplier list we need your products

2018-05-28 Thread Andrea Jung
gcc@gcc.gnu.org Here are some people you may know and would like to connect with you. Reach out and build new connections. Andrea Jung Chairperson and CEO of Avon Group of companies. View Profile Co

Re: GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction

2018-05-28 Thread Umesh Kalappa
Ok, thanks for the clarification jakub. Umesg On Mon, May 7, 2018, 2:08 PM Jakub Jelinek wrote: > On Mon, May 07, 2018 at 01:58:48PM +0530, Umesh Kalappa wrote: > > CCed Jakub, > > > > Agree that float division don't touch memory ,but fdiv result (stack > > > register ) is stored back to a me