On 11/25/20 2:58 AM, H.J. Lu via Gcc wrote:
On Tue, Nov 24, 2020 at 5:19 PM Joseph Myers wrote:
On Wed, 25 Nov 2020, (Cron Daemon) via Gccadmin wrote:
=== Working on: master ===
branch pulled and checked out
61 revisions since last Daily bump
Traceback (most recent call last):
File "../gc
On Tue, Nov 24, 2020 at 7:38 PM David Blaikie wrote:
>
> On Tue, Nov 24, 2020 at 3:11 AM Jakub Jelinek wrote:
> >
> > On Tue, Nov 24, 2020 at 12:04:45PM +0100, Mark Wielaard wrote:
> > > Hi,
> > >
> > > On Tue, 2020-11-24 at 08:50 +0100, Richard Biener wrote:
> > > > On Tue, Nov 24, 2020 at 8:45
On Wed, Nov 25, 2020 at 8:15 AM Marc Glisse wrote:
>
> On Wed, 25 Nov 2020, Ilya Leoshkevich via Gcc wrote:
>
> > I have a C floating point comparison (a <= b && a >= b), which
> > test_for_singularity turns into (a <= b && a == b) and vectorizer turns
> > into ((a <= b) & (a == b)). So far so go
On Wed, 2020-11-25 at 10:53 +0100, Richard Biener wrote:
> On Wed, Nov 25, 2020 at 8:15 AM Marc Glisse
> wrote:
> > On Wed, 25 Nov 2020, Ilya Leoshkevich via Gcc wrote:
> >
> > > I have a C floating point comparison (a <= b && a >= b), which
> > > test_for_singularity turns into (a <= b && a == b
> printf(“Hello World\n”); is UB under -fexec-charset= EBCDIC. WTF WTF!!!
It's not undefined behavior. It does, however, appear to trip various
bugs in GCC.
$ cat test.c
#include
int main(void) { printf("hello world\n"); }
$ gcc-9 --version | head -n1
gcc-9 (Debian 9.3.0-18) 9.3.0
$ gcc-9 -fex
On Wed, 25 Nov 2020, Siddhesh Poyarekar wrote:
> Would you agree to treating unnormals as NaNs and consequently have glibc
> provide that guarantee in the library instead of either declaring it undefined
> or maintaining the status quo, i.e. keeping it unspecified?
I think it would be a pain to m
On Wed, 25 Nov 2020, Richard Biener via Gcc wrote:
> > Hello,
> >
> > let me just mention the old
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53805
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53806
> >
> > There has been some debate about the exact meaning of -ftrapping-math, but
> > don
On Wed, Nov 25, 2020 at 1:22 AM Richard Biener
wrote:
>
> On Tue, Nov 24, 2020 at 7:38 PM David Blaikie wrote:
> >
> > On Tue, Nov 24, 2020 at 3:11 AM Jakub Jelinek wrote:
> > >
> > > On Tue, Nov 24, 2020 at 12:04:45PM +0100, Mark Wielaard wrote:
> > > > Hi,
> > > >
> > > > On Tue, 2020-11-24 at
I have to make filename work correctly under none UTF-8 exec charset. Do not
tell me to use locale since locale is not thread-safe and configure locale is a
huge issue.
I do not use any C stdio or C++ iostream facilities since I create my own I/O
library from scratch. However, this is something
On 11/26/20 12:57 AM, Joseph Myers wrote:
I think it would be a pain to maintain test coverage for unnormals (and
presumably all the other kinds of unsupported operands, and you'd need to
work out what semantics you want for pseudo-denormals as well since those
are the one kind of such representa
On 11/25/20 8:15 AM, Zack Weinberg wrote:
printf(“Hello World\n”); is UB under -fexec-charset= EBCDIC. WTF WTF!!!
It's not undefined behavior. It does, however, appear to trip various
bugs in GCC.
$ cat test.c
#include
int main(void) { printf("hello world\n"); }
$ gcc-9 --version | head -n1
Glibc cannot deal with EBCDIC or any other charset besides UTF-8 since GCC
itself does not emit exec-coding set to C library and C library just could not
deal with it.
Even glibc could deal with it, GCC allows different exec-charset to be linked
with each other which is definitely an undefined
12 matches
Mail list logo
