Hello Maciej,
On Sat, Mar 21, 2020 at 09:22:31PM +, Maciej W. Rozycki wrote:
[..]
> Spam bouncing is evil and often hits an innocent person
[..]
others like me might see it different:
Spam discarding is evil and often hits an innocent person.
Silently discarding a legal mail
Hi,
On Fri, Aug 25, 2017 at 09:55:29AM -0400, David Edelsohn wrote:
> On Fri, Aug 25, 2017 at 9:50 AM, Rainer Orth
> wrote:
> > Hi H.J.,
> >
> >> On Fri, Aug 25, 2017 at 6:32 AM, David Edelsohn wrote:
> >>> On Fri, Aug 25, 2017 at 9:24 AM, H.J. Lu wrote:
> On Fri, Aug 25, 2017 at 6:01 AM,
On Sun, Jan 19, 2014 at 07:39:12PM +0100, Winfried Magerl wrote:
> Hi,
>
> since "trunk revision 206525" I'm unable to bootstrap
> gcc with '-O3' as optimisation. No problem until
> revision 2065250.
>
> From the diff-output it looks like thi
High,
since "trunk revision 206525" I'm unable to bootstrap
gcc with '-O3' as optimisation. No problem until
revision 2065250.
>From the diff-output it looks like this entry from
ChangeLog is the only candidate:
---
diff -urN -x.svn gcc-head-206520/LAST_UPDATED gcc-head-206525/LA
Hi,
On Mon, May 20, 2013 at 09:40:52AM -0300, Adhemerval Zanella wrote:
> Hi,
>
> Thanks for reporting it, I saw it too when building glibc with gcc-trunk.
> Carlos O'Donell already reported it could be an issue to glibc at
> http://sourceware.org/ml/libc-alpha/2013-02/msg00299.html and I also no
Hi,
I've tried to compile upcoming glibc-2.18 with gcc-4.8.x and optimized
with '-O3' and testsuite breaks horrible with SIGSEGV and eating up
all available memory.
I've tracked it down to the flag 'tree-loop-distribute-patterns' and can
reproduce the problem with CFLAGS='-g -O2 -ftree-loop-distr
Hi,
looks like XOP/FAM4/FAM is responsible for the additional errors I
see when running gcc-testsuite or glibc-testsuite. I've opened Bug
56866 as a starting point, so the subject is a little bit misleading:
Bug 56866 - gcc 4.7.x/gcc-4.8.x with '-O3 -march=bdver2' misscompiles
glibc-2.17/crypt/s
Hi,
replacing my AMD Phenom2 with a AMD Piledriver (Bulldozer Version2)
was reason enough for me to recompile gcc (and the whole linux-system)
with hard optimisation set to bdver2 (as I've done since my first
linux on an 68030).
But this time an increasing number of errors makes me a little bit ne
