On (07/30/19 14:12), Sergey Senozhatsky wrote:
> On (07/29/19 09:42), Jonathan Wakely wrote:
> > Please don't cross-post to te gcc@ and gcc-bugs@ lists, that's never
> > appropriate.
>
> So is top-posing ;)
D'oh... s/posing/posting/
Will keep in mind next time that gcc team prefers bugzilla.
On (07/29/19 09:42), Jonathan Wakely wrote:
> Please don't cross-post to te gcc@ and gcc-bugs@ lists, that's never
> appropriate.
So is top-posing ;)
> The gcc@ list is not for reporting bugs, and the
> gcc-bugs@ list is for automated emails sent from our Bugzilla
> database, also not for reporti
Hi!
On Mon, Jul 29, 2019 at 07:37:53PM +0200, Martin Jambor wrote:
> as you might know, Tejas is our Google Summer of Code student working on
> adding built-in functions for some new math functions added in ISO/IEC
> TS 18661.
>
> His next step is to expand "functions rounding result to narrower
Hi Segher,
as you might know, Tejas is our Google Summer of Code student working on
adding built-in functions for some new math functions added in ISO/IEC
TS 18661.
His next step is to expand "functions rounding result to narrower type"
(so fadd, fsub and possibly fmul and fdiv described in
http:
Hi,
On Sat, Jul 27 2019, Tejas Joshi wrote:
> Hello.
>
>>> You'll need something different from CASE_MATHFN - these are a different
>>> kind of functions that need handling in a different way, because they are
>>> parametrized over certain *pairs* of types, rather than over a single
>>> type.
>> f
On Sunday, 28 July 2019 16:16:21 PDT Kevin Weidemann wrote:
> Hello everyone,
>
> I have recently randomly discovered the fact, that building with
> `-march=ivybridge` does not necessarily produce the same output as
> `-march=native` on an Intel Core i7 3770K (Ivy Bridge).
>
> In particular, `-ma
Please don't cross-post to te gcc@ and gcc-bugs@ lists, that's never
appropriate. The gcc@ list is not for reporting bugs, and the
gcc-bugs@ list is for automated emails sent from our Bugzilla
database, also not for reporting bugs. To report a bug please see
https://gcc.gnu.org/bugs/
Thanks.
On M
