Re: --enable-default-pie breaks kernel build on amd64

n, -no-pie) > +KBUILD_AFLAGS += $(call cc-option, -fno-pie) > +KBUILD_CPPFLAGS += $(call cc-option, -fno-pie) > + >  # The arch Makefile can set ARCH_{CPP,A,C}FLAGS to override the default >  # values of the respective KBUILD_* variables >  ARCH_CPPFLAGS := >  > thanks > 

Re: Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

LAGS to build kernel successfully. > > I'm currently looking for correct way to do this trick. > > -- Ben Hutchings Never put off till tomorrow what you can avoid all together. signature.asc Description: This is a digitally signed message part

Bug#869090: gcc-6: Address sanitizer: Shadow memory range interleaves

clash fix has broken ASan. The address space change that went into 4.11.11-1 and might have triggered this is "binfmt_elf: use ELF_ET_DYN_BASE only for PIE" (CVE- 2017-1000370, CVE-2017-1000371). This moved PIEs to lower addresses on x86 (starting at 0x400000 on i386 and 0x1 on amd4

Re: Bug#920286: gcc-8: Missing conflict/break with binutils-x86-64-linux-gnu:i386 can lead to broken compiler

gt; won't break any native stuff and it'll fix the bug at hand. > > Helmut -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

oblem for getting security updates out promptly. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part

Bug#970523: Missing fixes from gcc-10

Package: src:gcc-10-cross Version: 11 Severity: normal Please update to the current version of gcc-10. I am specifically running into PR96377 which was already fixed in the native compiler. Ben. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500,

Bug#1014851: Missing SLS mitigation (-mharden-sls) for x86

medium + + * Backport support for -mharden-sls for x86 + + -- Ben Hutchings Mon, 11 Jul 2022 15:02:37 +0200 + gcc-10 (10.2.1-6) unstable; urgency=medium * Update to git 20210110 from the gcc-10 branch. diff -Nru gcc-10-10.2.1/debian/patches/x86-add-mharden-sls-none-all-return-indirect-branch.

Bug#1014851: x86: Document new hardening options

Here's a patch for the documentation. This is a combination of the omitted parts of the 3 upstream commits that touched it. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. From: Ben Hutchings Date: Mon, 18 Jul 2022 15:50:38 +0200 Subject

Bug#1074608: sh port doesn't work with current gcc

Source: newlib Version: 4.4.0.20231231-3 Severity: important X-Debbugs-Cc: carl917...@packages.debian.org, gcc-sh-...@packages.debian.org The sh port of newlib assumes common data which is no longer the default behaviour of gcc. This results in a broken gcc-sh-elf: https://ci.debian.net/packages

Bug#506713: g++-4.3: Incorrect code in SPARC shared libraries

Package: g++-4.3 Version: 4.3.2-1 Severity: serious Functions compiled for SPARC with both -O2 and -fPIC options, which return structures and require global data, may have incorrect code generated for them. The following example is based on Qt 3, which is affected by this bug (see #490999). The

Bug#506713: g++-4.3: Incorrect code in SPARC shared libraries

On Mon, 2008-11-24 at 01:11 +0100, Matthias Klose wrote: > Ben Hutchings schrieb: > > Functions compiled for SPARC with both -O2 and -fPIC options, which > > return structures and require global data, may have incorrect code > > generated for them. > > please could yo

Bug#506713: Incorrect code in SPARC shared libraries

, offset1, %sp /* up to 10 instructions */ ld [ %sp + offset2 ], reg where offset1 + offset2 < 0 and reg is any register. Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: T

Re: Is this a gcc or a kernel bug?

onsole (not X) before running this program, so that you can see any kernel messages that would help us to track down the bug. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky signature.asc Description: This is a digitally signed message part

Re: C++ symbol mangling difference between arches

tance would be represented by a back-reference ("S_" or "S" "_"), whereas on others they would be different and the second would be represented independently. Ben. -- Ben Hutchings It is impossible to make anything foolproof because fools are so ingenious. signature.asc Description: This is a digitally signed message part

Re: C++ symbol mangling difference between arches

t a different symbol mangling, but different code. > qreal is a typedef to either float or douxble wrapped in a ifdef. This is *exactly* like the other cases, except it's not one of the standard C++ or POSIX type aliases. Ben. -- Ben Hutchings It is impossible to make anything foolproo

Re: C++ symbol mangling difference between arches

e inheritance and good style of C++ programming :/ So this issue is > important. > > So which way to choose: 2a or 2b or another? [...] Would it be possible to implement expansion to a regexp instead of to a string that must exactly match? Ben. -- Ben Hutchings 73.46% of all statistics a

Bug#356435: g++-4.1: may fail to generate code for base destructor defined inline

reassign 356435 g++-4.0 retitle 356435 g++-4.0: may fail to generate all versions of inline destructor found 356435 4.0.2-5 thanks I'm reassigning and retitling this based on information in the upstream bug report. Ben. -- Ben Hutchings If you seem to know what you are doing, you'l

Bug#356316: Patch for -Wnon-virtual-dtor

/ { dg-bogus "non-virtual destructor" } +public: + virtual void bar(); +protected: + ~foo(); +}; -- END -- and an entry for the changelog: 2006-04-23 Ben Hutchings <[EMAIL PROTECTED]> PR c++/7302 * class.c: Do not warn about protected or private non-virtual

Bug#361707: Causes FTBFS with GCC 4.2: '' has incomplete type

This is now C++ core DR 577: http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html#577 -- Ben Hutchings Every program is either trivial or else contains at least one bug signature.asc Description: This is a digitally signed message part

Bug#356435: fixed in gcc-4.1 4.1.1-8

m the archive. (Also, it may be necessary to rebuild some libraries that were built with g++-4.0, if this hasn't already happened.) Ben. -- Ben Hutchings -- [EMAIL PROTECTED] shortened to [EMAIL PROTECTED] If you've signed my GPG key, please send a signature on and to the new uid. Theory a

Bug#380541: gcc: Wrong code for hoisted multiplication

Package: gcc Version: 4:4.1.1-5 Severity: important gcc generates wrong code for solo.c in sgt-puzzles, leading to a segment violation. Ben. -- Ben Hutchings -- [EMAIL PROTECTED] shortened to [EMAIL PROTECTED] If you've signed my GPG key, please send a signature on and to the ne

Bug#380541: gcc: Wrong code for hoisted multiplication

that patch or Debian's 4.1.1-15 + that patch? 17:36 < pinskia> 4.1.2 17:36 < pinskia> so the 4.1 branch + that patch 17:37 < Womble2> oh right 17:37 < Womble2> gcc version 4.1.2 20060928 (prerelease) (Debian 4.1.1-15) 17:37 < Womble2> probabl

Bug#609690: Debian x86 32-bits built for i586 !?

e options for '586' and '586 with TSC', both of which result in -m586, so gcc does not appear to assume the existence of rdtsc. I would not expect gcc to generate cmpxchg8 except through an intrinsic, but I could be wrong. Ben. -- Ben Hutchings Once a job is fouled up, an

Bug#609690: Debian x86 32-bits built for i586 !?

ts 486-class processors is more of an aspiration. What maintainer has the time to test on such antiques regularly? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part

Building kernel with gcc-4.5

I'm changing the kernel compiler to gcc-4.5 in experimental. I understand this was not a good version for alpha, hppa or m68k so I have left them with gcc-4.4, but this can be changed on request from the porters. We will probably need to move on to gcc-4.6 before wheezy. Ben. -- Ben Hutc

Increasing minimum 'i386' processor

ted until early 2009 (#511703), suggesting that there were few users with such systems. Debian 7.0 'wheezy' should be released in late 2012 or early 2013 and in the intervening 4 years the numbers of running systems with such a processor will have declined still further. Ben. -- Ben Hutchings

Re: Increasing minimum 'i386' processor

On Tue, Nov 22, 2011 at 04:47:20PM +, Ian Jackson wrote: > Ben Hutchings writes ("Increasing minimum 'i386' processor"): > > The 486-class processors that would no longer be supported are: > > 1. All x86 processors with names including '486' >

Re: Increasing minimum 'i386' processor

On Wed, 2011-11-23 at 00:44 +0100, Matthias Klose wrote: > On 11/19/2011 11:42 PM, Ben Hutchings wrote: > > The i386 architecture was the first in Linux and in Debian, but we have > > long since dropped support for the original i386-compatible processors > > and now requi

Bug#356316: g++-4.0: -Wnon-virtual-dtor and -Wall produce false warnings

Package: g++-4.0 Version: 4.0.2-10 Severity: normal Tags: upstream It's generally a design error to have a public non-virtual destructor in a class that has virtual functions, so I accept that g++ should warn about that. However, a protected non-virtual destructor is normally fine, because it pre

Bug#356316: g++-4.0: -Wnon-virtual-dtor and -Wall produce false warnings

EE_PRIVATE (dtor) || TREE_PROTECTED (dtor warning (0, "%q#T has virtual functions but non-virtual destructor", t); } -- END -- This could probably do with a test case, and maybe rewording of the warning to match the tighter test. Ben. -- Ben Hutchings We ge

Bug#356435: g++-4.1: may fail to generate code for base destructor defined inline

Package: g++-4.1 Version: 4.1.0-0 Severity: important Where a base class has a destructor defined inline, g++ may generate code for a derived class's destructor that calls an non-inline version of the base class destructor, but without generating code for the latter. This is normally masked by th

Bug#356548: Processed: probably a compiler bug

ata, int filenumber) { return ((const MAINPACKET*)packetdata)->fileid[filenumber]; } const MD5Hash& SetId(const char *packetdata) { return ((const MAINPACKET*)packetdata)->header.setid; } // END SetId provokes the error; FileId doesn't. Ben. -- Ben Hutchings One of the nice

Bug#392559: avifile build failure

END -- I don't know whether the resulting code works though... > Apparently that the only package in testing failing with the current > gcc-4.1. That's because we don't have enough unit tests to find the subtle code generation bugs. Ben. -- Ben Hutchings -- [EMAIL PROTECT

Bug#827136: Cross-compiler packages cannot be build-depended on

Package: src:gcc-5-cross Version: 23 Severity: normal I am looking into making the linux source package cross-buildable in a standard way. This requires replacing a build-dependency of e.g.: gcc-5 [...] with: gcc-5 [...] , gcc-5-alpha-linux-gnu:any [alpha] , ... Unfortunately this is

Bug#827136: Cross-compiler packages cannot be build-depended on

On Sun, 2016-06-12 at 20:41 +0100, Ben Hutchings wrote: > Package: src:gcc-5-cross > Version: 23 > Severity: normal > > I am looking into making the linux source package cross-buildable in a > standard way.  This requires replacing a build-dependency of e.g.: > >   

Bug#827136: fixed in gcc-5-cross 24

Control: reopen -1 Control: notfixed -1 24 On Thu, 14 Jul 2016 09:51:35 +0300 Александр Волков wrote: > It's still not fixed in gcc-5-cross-24. > There is the entry about fixes in the changelog, but there are no fixes  > in the control files. Indeed, this wasn't fixed. Ben.

Bug#717557: gcc-4.8: can't compile working 64bit kernel with 32bit userspace gcc-4.8

ssibly cause other problems, and neither the pre-included header nor the fact that -nostdinc disables it seem to be documented. Ben. -- Ben Hutchings Time is nature's way of making sure that everything doesn't happen at once. signature.asc Description: This is a digitally signed message part

Bug#717557: gcc-4.8: can't compile working 64bit kernel with 32bit userspace gcc-4.8

and neither the pre-included header nor the fact that -nostdinc disables > > it seem to be documented. > > please attach the test program and the command line options used for this test > case. I think the issue is within the kernel build system not being prepared > for multiarc

Bug#726867: Internal compiler error while building Linux drivers/media/dvb-core/dvb_demux.c

Package: gcc-4.8 Version: 4.8.2-1 Severity: important linux 3.11.5-1 failed to build on both mips and mipsel: CC [M] drivers/media/dvb-core/dvb_demux.o /«PKGBUILDDIR»/drivers/media/dvb-core/dvb_demux.c: In function 'dvb_dmx_swfilter_packet': /«PKGBUILDDIR»/drivers/media/dvb-core/dvb_demux.c:4

Bug#717557: gcc-4.8: can't compile working 64bit kernel with 32bit userspace gcc-4.8

On Sun, 2013-10-20 at 22:21 +0200, Matthias Klose wrote: > Am 20.10.2013 00:25, schrieb Ben Hutchings: > > On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote: > >> Control: severity -1 important Control: tags -1 + moreinfo > >> > >>>> In file inc

Bug#717557: gcc-4.8: can't compile working 64bit kernel with 32bit userspace gcc-4.8

On Sun, 2013-10-20 at 23:44 +0200, Matthias Klose wrote: > Am 20.10.2013 22:58, schrieb Ben Hutchings: > > On Sun, 2013-10-20 at 22:21 +0200, Matthias Klose wrote: > >> Am 20.10.2013 00:25, schrieb Ben Hutchings: > >>> On Sat, 2013-10-19 at 23:38 +0200, Matthi

Bug#726867: ICE while building Linux dvb_demux.c for MIPS64 with -Os

Control: retitle -1 ICE while building Linux dvb_demux.c for IA64 or MIPS64 with -Os The same function caused ICE on ia64, and the test case also causes ICE at all optimisation levels except -O0. Ben. -- Ben Hutchings [W]e found...that it wasn't as easy to get programs right as we had th

Bug#757835: nfs-kernel-server: after update 1.2.8-6->1.2.8-8 rpc.mountd starts crashing

#x27;t be null, so there is no need to check whether it is. I.e. this is a bug in nfs-utils, not the compiler. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part

Bug#757835: nfs-kernel-server: after update 1.2.8-6->1.2.8-8 rpc.mountd starts crashing

On Tue, 2014-08-12 at 19:23 +0100, Ben Hutchings wrote: > On Tue, 2014-08-12 at 09:05 -0700, Steve Langasek wrote: > [...] > > Matthias, could you please have a look at the below test case? We have a > > regression in the latest nfs-kernel-server build, which appears to be cause

Bug#757835: nfs-kernel-server: after update 1.2.8-6->1.2.8-8 rpc.mountd starts crashing

On Tue, 2014-08-12 at 20:54 +0200, Sven Joachim wrote: > On 2014-08-12 20:23 +0200, Ben Hutchings wrote: > > > On Tue, 2014-08-12 at 09:05 -0700, Steve Langasek wrote: > > [...] > >> Matthias, could you please have a look at the below test case? We have a > >>

Bug#765380: don't ship gcc-4.8 with jessie

. I expect that x86, arm*, arm64, and powerpc* kernels have been well- tested with gcc 4.9. Out of our release architectures, that would leave mips and mipsel as unknown. Ben. -- Ben Hutchings [W]e found...that it wasn't as easy to get programs right as we had thought. ... I realized

Bug#785066: -m32 no longer supported on ppc64el; cannot build a kernel

Package: gcc-4.9 Version: 4.9.2-16 Severity: serious In : /«PKGBUILDDIR»/arch/powerpc/kernel/vdso32/gettimeofday.S: Assembler messages: /«PKGBUILDDIR»/arch/powerpc/kernel/vdso32/gettimeofday.S:42: Err