Bug#1000398: fixed upstream

2021-11-27 Thread Nick Lewycky
You don't even need to use std::valarray, a one-line testcase file with "#include " fails to compile in clang in C++17 mode or newer. A fix for this issue was committed to libstdc++ on Nov 5th: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=2b2d97fc545635a0f6aa9c9ee3b017394bc494bf Would it be

Bug#600888: g++-4.4: [armel, fixed in head] gcc may miscompile "x >> 1"

2010-10-20 Thread Nick Lewycky
On 20 October 2010 21:32, Matthias Klose wrote: > On 21.10.2010 01:43, Nick Lewycky wrote: > >> Package: g++-4.4 >> Version: 4.4.5-4 >> Severity: normal >> >> >> This version of gcc has a bug where code that does a shift-right >> by literal

Bug#600888: g++-4.4: [armel, fixed in head] gcc may miscompile "x >> 1"

2010-10-20 Thread Nick Lewycky
http://gcc.gnu.org/ml/gcc-patches/2010-09/msg01070.html which has already been accepted into gcc head, but I didn't see it get applied to the release branches. Please add this patch as a debian-local change. Thanks! Nick Lewycky -- System Information: Debian Release: squeeze/sid APT prefer

Bug#523869: libffi-dev: gcc doesn't find ffi.h

2009-04-13 Thread Nick Lewycky
Package: libffi-dev Version: 3.0.7-1 Severity: important It seems that libffi-dev puts ffi.h in a target-specific directory on each platform. For example, on my system it's in /usr/include/i486-linux-gnu/ which is a directory that is used by absolutely no other package in Debian. Notably, gcc doe

Bug#492505: gcc-4.3: regression from 4.2, ICE in set_lattice_value, at tree-ssa-ccp.c:487

2008-07-26 Thread Nick Lewycky
Package: gcc-4.3 Version: 4.3.1-6 Severity: normal The attached delta-reduced code crashes GCC 4.3 with -O1, but not -O0 or GCC 4.2.4 (Debian 4.2.4-3). # gcc-4.3 000.c -c -O1 000.c: In function ‘_ov_64_seek_lap’: 000.c:33: internal compiler error: in set_lattice_value, at tree-ssa-c

Bug#491653: gcc-4.3: misoptimization of 64-bit bitfield when not byte aligned

2008-07-21 Thread Nick Lewycky
close 491653 thanks Hi Bastian, You're right again, this is entirely due to the effects of strict aliasing rules. The problem goes away with -fno-strict-aliasing. Nick Bastian Blank wrote: On Sun, Jul 20, 2008 at 11:14:10PM -0700, Nick Lewycky wrote: This testcase produces diff

Bug#491654: gcc-4.3: _Bool isn't wide enough.

2008-07-21 Thread Nick Lewycky
r the trouble. Nick Bastian Blank wrote: On Sun, Jul 20, 2008 at 11:32:28PM -0700, Nick Lewycky wrote: In C99, _Bool is required to map to one of the unsigned types (6.2.5/6). Please quote the standard. I read something different there. However, GCC rejects the following (admittedly unet

Bug#491654: gcc-4.3: _Bool isn't wide enough.

2008-07-20 Thread Nick Lewycky
Package: gcc-4.3 Version: 4.3.1-6 Severity: normal In C99, _Bool is required to map to one of the unsigned types (6.2.5/6). On i586, this is 'unsigned char', by ABI. That means that you get eight bits to the _Bool. However, GCC rejects the following (admittedly unethical) snippet: struct S7 {

Bug#491653: gcc-4.3: misoptimization of 64-bit bitfield when not byte aligned

2008-07-20 Thread Nick Lewycky
Package: gcc-4.3 Version: 4.3.1-6 Severity: normal This testcase produces different output depending on whether -O1 or -O2 is specified. Correct: # gcc PR1386.c -o pr1386 -O1 PR1386.c: In function ‘main’: PR1386.c:15: warning: large integer implicitly truncated to unsigned typ

Bug#386121: (no subject)

2006-09-06 Thread Nick Lewycky
reakage without an associated so-version bump. Nick Lewycky -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361024: Simple test case [Was: libstdc++.so.6: cannot handle TLS data]

2006-04-06 Thread Nick Lewycky
urprised. Anyways, running the modern ldconfig fixes my problem and allows the apps to find the proper libraries. Sorry for the confusion. Thanks, Nick Lewycky -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361024: Simple test case [Was: libstdc++.so.6: cannot handle TLS data]

2006-04-06 Thread Nick Lewycky
Matthias Klose wrote: > Does /etc/ld.so.nohwcap exist? What happens if you (re)move it? No it doesn't. I do have an /etc/ld.so.hwcappkgs, if that's related. It contains: libc6 2.3.6-5 libc6-i686 2.3.6-5 Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Tro

Bug#361024: Simple test case [Was: libstdc++.so.6: cannot handle TLS data]

2006-04-06 Thread Nick Lewycky
bug go away: export LD_LIBRARY_PATH=/lib/tls /lib/tls isn't in my /etc/ld.so.conf. Should it be? When did that change? And what about the subdirectories under /lib/tls? What package is supposed to install/own/update the ld.so.conf? Nick Lewycky -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] w

Bug#361024: Simple test case [Was: libstdc++.so.6: cannot handle TLS data]

2006-04-06 Thread Nick Lewycky
. That would explain its non-deterministic nature. Valgrind output also attached. Nick Lewycky demo.ld.bz2 Description: Unix tar archive demo.valgrind.bz2 Description: Unix tar archive

Bug#361024: libstdc++6: cannot handle TLS data

2006-04-06 Thread Nick Lewycky
severity 361024 critical thanks dude Justification: breaks unrelated software This bug is causing total breakage of apt-show-versions. It's also causing problems with dia and gnucash (unable to load plugins written in C++) and possibly other software in the archive. Nick Lewycky -