Hi all,
The 5th LLVM/GCC social in Nanjing will happen on Jan 19, 2019.
Everyone interested in LLVM/GCC/Toolchain/IDE related projects is
invited to join.
Event details is at https://mp.weixin.qq.com/s/7jupkPiRrlxjYEuglMbvFA
BoF style. Presentations are welcome :-)
Looking forward to meet you !
On Mon, 7 Jan 2019 at 15:51, nick wrote:
>
>
>
> On 2019-01-07 10:44 a.m., Jonathan Wakely wrote:
> > On Mon, 7 Jan 2019 at 15:42, nick wrote:
> >>
> >> Greetings All,
> >>
> >> I was wondering as I sent a patch before the holidays if I should resend it
> >> as I did not get any replies.
> >
> > W
On 2019-01-07 10:44 a.m., Jonathan Wakely wrote:
> On Mon, 7 Jan 2019 at 15:42, nick wrote:
>>
>> Greetings All,
>>
>> I was wondering as I sent a patch before the holidays if I should resend it
>> as I did not get any replies.
>
> Which patch? I don't see any patch from you that didn't get som
On Mon, 7 Jan 2019 at 15:42, nick wrote:
>
> Greetings All,
>
> I was wondering as I sent a patch before the holidays if I should resend it
> as I did not get any replies.
Which patch? I don't see any patch from you that didn't get some replies.
Greetings All,
I was wondering as I sent a patch before the holidays if I should resend it
as I did not get any replies.
Thanks,
Nick
Status
==
Stage 3 is done now.
Changes of GCC trunk should now be restricted to regression and documentation
fixes. That is, it is in the same mode as the open release branches we have.
As soon as the count of P1 bugs drops to zero (and un-categorized, aka P3
bugs have been categorized) yo
> On Mon, Jan 07, 2019 at 09:29:09AM +0100, Richard Biener wrote:
> > On Sun, 6 Jan 2019, Jan Hubicka wrote:
> > > Even though it is late in release cycle I wonder if we can do that for
> > > GCC 9? Performance of vectorization is very architecture specific, I
> > > would propose enabling vectoriz
On Mon, Jan 07, 2019 at 09:29:09AM +0100, Richard Biener wrote:
> On Sun, 6 Jan 2019, Jan Hubicka wrote:
> > Even though it is late in release cycle I wonder if we can do that for
> > GCC 9? Performance of vectorization is very architecture specific, I
> > would propose enabling vectorization for
> > Note that I benchmarked -ftree-slp-vectorize separately before and
> > results was hit/miss, so perhaps enabling only -ftree-vectorize would
> > give better compile time tradeoffs. I was worried of partial memory
> > stalls, but I will benchmark it and also benchmark difference between
> > cost
> Note that I benchmarked -ftree-slp-vectorize separately before and
> results was hit/miss, so perhaps enabling only -ftree-vectorize would
> give better compile time tradeoffs. I was worried of partial memory
> stalls, but I will benchmark it and also benchmark difference between
> cost models.
4G camera !!!
Hi dear gcc,
How are you?
This is ZYsecurity co.,ltd new 4G Wireless WiFi Bullet cameras.
Support:
* Audio/SD card/Wireless WiFi/4G/Reset bullon/APP:CamHi
If you have interested in this products welcome to contact me to get more
details.
Looking forward to hear from you soon.
On Sun, 6 Jan 2019, Jan Hubicka wrote:
> Hello,
> while running benchmarks for inliner tuning I also run benchmarks
> comparing -O2 and -O2 -ftree-vectorize -ftree-slp-vectorize using Martin
> Liska's LNT setup (https://lnt.opensuse.org/). The results are
> summarized below but you can also see a
12 matches
Mail list logo
