Huh, sorry. Must have been a mis-click, I just wanted to subscribe to
the bug I think. I've removed the flag now.
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems this was a known common-code issue that is fixed in mainline
not in LLVM 10. There's already a bug to port it to 10.0.1 (PR45272)
with a back ported patch https://reviews.llvm.org/D76596.
Can you try whether this fixes the problem?
--
You received this bug notification because you are
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867173
Title:
FTBFS with llvm-10
To manage notifications about this bug go to:
Moving section headers to the end sounds good.
However, maybe we should make the bfd_from_remote_memory change too, in
order to cope with kernels already in the field?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, GDB assumes that the VDSO contains the whole ELF *file*, not just
segments that would be loaded into memory if the object were loaded by
the dynamic loader.
In particular, none of the symbol table (.symtab, .strtab) or debug info
sections usually reside in loaded segments, but the debugger
Hmmm ... usually, the section headers come at the very end of the file.
It's a bit strange that there is section data *after* the headers in
this case; maybe that's what confuses GDB/BFD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On second glance, looks I'm wrong: .symtab and .strtab actually do come *after*
the section headers in normal executables too.
So I guess the best thing to do would be to fix bfd_from_remote_memory to
actually include enough memory to cover all sections, even those after the
section headers.
Anton Blanchard wrote:
I wonder if the gdb complaint about the kernel VDSO is causing the test to
fail. The warning is almost certainly a result of
this kernel patch:
powerpc: Use unstripped VDSO image for more accurate profiling data
Whether or not this complaint is causing that test to
So based on this patch:
https://sourceware.org/ml/binutils/2014-04/msg00283.html
I think bfd_elf64_powerpc_vec has been renamed to powerpc_elf64_vec.
Alan, can you verify?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So there's two issues:
First of all, on amd64:
g++ -std=c++0x -dM -E - /dev/null | grep linux
cc1: warning: command line option -std=c++0x is valid for C++/ObjC++ but not
for C
#define __linux 1
#define __linux__ 1
#define __gnu_linux__ 1
#define linux 1
Note the warning? That means the
** Changed in: gcc-linaro-tracking
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675347
Title:
volatile int causes inline assembly build failure
To
I've checked in a backport of Richard's fix to Linaro GCC 4.6. Other
series are not affected.
** Changed in: gcc-linaro
Milestone: None = 4.6-2012.05
** Changed in: gcc-linaro
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of
Committed backports to Linaro GCC 4.6 and 4.7.
** Also affects: gcc-linaro/4.6
Importance: Undecided
Status: New
** Also affects: gcc-linaro/4.7
Importance: Medium
Assignee: Ulrich Weigand (uweigand)
Status: In Progress
** Changed in: gcc-linaro/4.6
Importance
** Branch linked: lp:~uweigand/gcc-linaro/lp-972648-4.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972648
Title:
ICE (segfault) in gsi_for_stmt
To manage notifications about this bug go to:
** Branch linked: lp:~uweigand/gcc-linaro/lp-968766-4.7
** Branch linked: lp:~uweigand/gcc-linaro/lp-968766-4.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968766
Title:
GCC 4.6.3 (cc1) crashes
This affects current FSF mainline as well. I've opened a GCC bugzilla report:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52870
** Bug watch added: GCC Bugzilla #52870
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52870
** Changed in: gcc-linaro
Status: Triaged = In Progress
--
You
A minimal (C) test case (with -O -ftree-vectorize) for me is:
struct test
{
unsigned long exp[0];
};
void test (struct test *a, long b, unsigned long bitmask)
{
if (b 0)
{
a-exp[0] = ~bitmask;
a-exp[0] |= b;
}
else
{
a-exp[0] = ~bitmask;
}
}
The problem
Yes, the fix is present in GDB 7.4 (and in fact already GDB 7.3)
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523959
Title:
GDB backtrace does not work correctly for Thumb-2 on armel
To
** Changed in: gcc-linaro
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600209
Title:
getfem++ fails to build from source in linaro
To manage notifications
Maybe I'm missing something, but as I understand those *are* valid VFPv3
(even VFPv2) instructions, not just NEON instructions ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937864
Title:
Note that all this is decided by the kernel's mmap area allocation
strategy; see the various get_unmapped_area routines in platform-
specific kernel code (e.g arch/arm/mm/mmap.c:arch_get_unmapped_area vs.
x86/kernel/sys_x86_64.c:arch_get_unmapped_area_topdown).
If any change is required here (and
I've now installed the updated FPGA bitfiles on my VE, and this does
indeed appear to fix the problems I've been seeing. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673820
Title:
I'm running into this issue with failing network connections on vexpress
while trying to run the GDB testsuite in remote mode ...
Has there been any progress on this bug in the meantime?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've verified that the problem is fixed with 2.13-0ubuntu9. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684218
Title:
Failure to backtrace out of glibc system call stubs
--
ubuntu-bugs
GDB part of the fix now committed.
** Also affects: eglibc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdb-linaro
Status: In Progress = Fix Committed
** Changed in: gdb-linaro
Milestone: None = 7.2-2011.04-0
--
You received this bug notification because you
glibc part of the fix is now committed to libc-ports:
[PATCH][arm] Create ARM unwind records for system call stubs
http://sourceware.org/ml/libc-ports/2011-03/msg00035.html
http://sourceware.org/ml/glibc-cvs/2011-q1/msg00119.html
commit 738860089d5c510f3445f9830d9924ab58659c51
Can this be
The main change (support for .ARM.exidx unwind info) is already in
Ubuntu GDB (came in with the Linaro GDB merge).
There is one minor additional fix (actually a pre-existing bug in the ARM
prologue parser exposed by the glibc change) that is not yet in Ubuntu GDB.
This extra fix has been
When you say:
On the intel machine using gdb-mutliarch
gdb-multiarch /bin/ls
are you actually refering to the Intel copy of /bin/ls ?
This will cause GDB to expect to debug Intel architecture, which does
not agree with an ARM architecture being reported by the remote stub.
You should use a
** Changed in: gdb-linaro
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728216
Title:
GDB fails to get a valid backtrace while debugging a Webkit SIGSEGV
--
It seems webkit has a JIT that generates assembler code at runtime. The
crash happens while executing one of those generated blocks of code.
Since there is no debug or unwind information, or even basic symbol
information, available for such generated code, there really is not much
GDB can do
** Changed in: gcc-linaro
Milestone: None = 4.5-2011.02-0
** Changed in: gcc-linaro
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685352
Title:
It turns out there is no other problem on 4.6. The compiler in the
ubuntu-toolchain-r/test ppa does not build Python at all due to PR
47271. After adding the fix for this PR to the ppa package, the
compiler runs into the exact same problem as described for 4.5 in the
previous comment. By using
I've now reproduced and analyzed the problem on i386 with GCC 4.5, i.e.
building python3.2-3.2~rc1 using the 4.5.1-1ubuntu3 compiler.
It turns out that there is no particular bug here (the CFG looks
identical in the -fprofile-generate and -fprofile-use cases), but
instead we're running in a known
Upstream GCC patch committed here:
http://gcc.gnu.org/viewcvs?root=gccview=revrev=168944
I'll backport to Linaro GCC 4.5.
** Changed in: gcc-linaro
Status: Confirmed = In Progress
** Changed in: gcc-linaro
Assignee: (unassigned) = Ulrich Weigand (uweigand)
--
You received
Backport proposed for merge:
https://code.launchpad.net/~uweigand/gcc-linaro/lp-685352/+merge/46663
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685352
Title:
libplymouth2_0.8.2-2ubuntu6 and later
** Changed in: gcc-linaro
Status: New = Confirmed
** Changed in: gcc-linaro
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685352
Title:
doko asked me to look into this. This is definitely a compiler bug.
The minimal test case I get is:
unsigned short test (unsigned char val) __attribute__ ((noinline));
unsigned short
test (unsigned char val)
{
return val * 255;
}
int
main(int argc, char**argv)
{
printf (test(val=40) =
Opened upstream gcc bug report PR rtl-optimzation/47299
** Bug watch added: GCC Bugzilla #47299
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47299
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47299
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685352
Title:
libplymouth2_0.8.2-2ubuntu6 and later give ragged splash and text
rendering
--
I just successfully completed a profiled build of python3.2_3.2~b2-1.dsc
on armel Natty using the Ubuntu/Linaro 4.5.1-10ubuntu3 system compiler,
so the problem seems to no longer exist on 4.5.
Do we still care about 4.4 at this point?
--
You received this bug notification because you are a
This is probably a duplicate of #701733 ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/701988
Title:
ICE on ix86 (-m64) with Linaro 2011-01
--
ubuntu-bugs mailing list
I've now committed a patch to mainline GDB that significantly improves
backtraces for Thumb-2 code even in the absence of DWARF CFI debug info. This
will still not handle absolutely all cases (e.g. hand-written assembler
routines that don't follow usual conventions), but should still help
** Changed in: gdb-linaro
Assignee: (unassigned) = Ulrich Weigand (uweigand)
--
GDB backtrace does not work correctly for Thumb-2 on armel
https://bugs.launchpad.net/bugs/523959
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: gdb-linaro
Status: In Progress = Fix Committed
** Changed in: gdb-linaro
Milestone: None = 7.2-2010.10-0
--
GDB backtrace does not work correctly for Thumb-2 on armel
https://bugs.launchpad.net/bugs/523959
You received this bug notification because you are a member of
** Changed in: gcc-linaro/4.5
Status: In Progress = Fix Committed
--
firefox fails to build from source with Linaro toolchain
https://bugs.launchpad.net/bugs/604874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: gcc-linaro/4.4
Status: In Progress = Fix Committed
--
firefox fails to build from source with Linaro toolchain
https://bugs.launchpad.net/bugs/604874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: gcc-linaro
Status: In Progress = Fix Committed
--
bootstrap failure in stage3 (integer overflow in preprocessor expression)
https://bugs.launchpad.net/bugs/500524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hmm, I was unable to reproduce any failures with getfem++-4.0.0-4ubuntu2
even on your machine.
However, I *am* seeing failures with the current maverick version,
getfem++-4.1-1ubuntu1 :
../bilaplacian /tmp/elas.param_382 -d NX=4 21 failed
The MUMPS user guide says about error -9:
–9 Main internal real/complex workarray S too small. If INFO(2) is positive,
then the number of entries
that are missing in S at the moment when the error is raised is available in
INFO(2). If INFO(2) is
negative, then its absolute value should be
Incrementing ICNTL(14) one by one results in ever decreasing values of
INFO(2) in the error return case, down until 40 if the ICNTL(14) line
is changed to +=44. When going to += 45, the test case succeeds
without error.
All this doesn't look like a compiler problem to me, just a
configuration
g++ -fmessage-length=0 -c -fno-omit-frame-pointer -Os -fno-strict-aliasing
datetime.ii
succeeds with no error on
g++-4.4.real (Ubuntu/Linaro 4.4.4-8ubuntu1) 4.4.5 20100728 (prerelease)
This might have been fixed by the Linaro compiler ...
--
[armel] unable to find a register to spill in
Interesting. I just tried the very same build, and it works for me ...
Is the failure reproducible on your system?
--
getfem++ fails to build from source in linaro
https://bugs.launchpad.net/bugs/600209
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This actually has nothing to do with Linaro GCC, the problem is simply
that a current mainline snapshot cannot compile an unmodified 4.4 branch
Ada compiler.
On 2010-06-22, revision 161147 was checked into mainline GCC:
http://gcc.gnu.org/viewcvs?view=revisionrevision=161147
This revision
** Also affects: gcc-linaro/4.4
Importance: Undecided
Status: New
** Also affects: gcc-linaro/4.5
Importance: High
Assignee: Ulrich Weigand (uweigand)
Status: In Progress
** Changed in: gcc-linaro/4.4
Assignee: (unassigned) = Ulrich Weigand (uweigand)
** Changed
Merge requests for both Linaro GCC 4.4 and Linaro GCC 4.5 now pending.
** Branch linked: lp:~uweigand/gcc-linaro/lp-604874-4.5
--
firefox fails to build from source with Linaro toolchain
https://bugs.launchpad.net/bugs/604874
You received this bug notification because you are a member of Ubuntu
Merge request into Linaro GCC 4.4 now pending.
--
bootstrap failure in stage3 (integer overflow in preprocessor expression)
https://bugs.launchpad.net/bugs/500524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Fix checked in to 4.5 branch as well.
--
firefox fails to build from source with Linaro toolchain
https://bugs.launchpad.net/bugs/604874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Fix approved for GCC mainline and checked in. Will check in to 4.5 branch
after 4.5.1 release.
Preparing backport to Linaro GCC now.
--
firefox fails to build from source with Linaro toolchain
https://bugs.launchpad.net/bugs/604874
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 595479 ***
https://bugs.launchpad.net/bugs/595479
** This bug has been marked a duplicate of bug 595479
Sequel to PR40521 -- -g causes GCC to generate .eh_frame
--
sequel to PR40521
https://bugs.launchpad.net/bugs/604653
You received this bug
** Also affects: gcc-4.4 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gcc-4.5 (Ubuntu)
Importance: Undecided
Status: New
--
Sequel to PR40521 -- -g causes GCC to generate .eh_frame
https://bugs.launchpad.net/bugs/595479
You received this bug notification
I'm getting the ICE on this test case even on a *native* x86 build of
vanilla GCC 4.4.4 release (only when using -fstack-protector, of
course). Native PPC test fails as well (a bit differently). So this
does not appear to be specific to either ARM or the Linaro patches.
--
[armel] additional
** Changed in: gcc-linaro
Status: New = Fix Committed
--
[armel, fixed in 4.5] ICE in find_reloads, at reload.c in thumb mode
https://bugs.launchpad.net/bugs/517156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The problem is that cfgexpand.c wants to track conflicts between each
pair of stack variables in order to decide whether they can share a
stack slot or not -- and this test case has 10 variables, which
means 5 billion potential conflict pairs. This overflows a size_t value
on 32-bit host
Looks like this has been addressed in 4.5 and later by Bernd Schmidt's patch
for PR 41718:
http://gcc.gnu.org/ml/gcc-patches/2009-11/msg00682.html
and Michael Matz's subsequent patch for PR 38582:
http://gcc.gnu.org/ml/gcc-patches/2009-12/msg00144.html
--
[armel] additional testsuite failures
Since this only occurs with pathological source code, my recommendation
would be to leave this as won't fix for 4.4; with 4.5 we get the fix
from upstream anyway.
--
[armel] additional testsuite failures with -mthumb (compared to -marm)
https://bugs.launchpad.net/bugs/497295
You received this
Linaro GCC actually contains a backport of the PR 42748 fix, so this
should be fixed now.
** Changed in: gcc-linaro
Status: New = Fix Released
--
[PR42748, armel] excess errors in libstdc++ testsuite when built with glibc-2.11
https://bugs.launchpad.net/bugs/505829
You received this bug
This is a duplicate to 595479, right?
--
sequel to PR40521
https://bugs.launchpad.net/bugs/604653
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Also affects: gcc-linaro/4.4
Importance: Undecided
Status: New
--
[armel] additional testsuite failures with -mthumb (compared to -marm)
https://bugs.launchpad.net/bugs/497295
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gcc-linaro
Status: New = Confirmed
--
[armel] gnat-4.4 built from the linaro toolchain fails to build
https://bugs.launchpad.net/bugs/608125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The problem is in the operator== and operator!= routines for UUID, in
include/xplc/uuidops.h:
inline int operator==(const UUID uuid1, const UUID uuid2) {
return
(uuid1 == uuid2) ||
((static_castconst u_int32_t*(uuid1.Data1)[0] == static_castconst
u_int32_t*(uuid2.Data1)[0])
The error message is odd, since at this location the type Hnum *is*
used.
Maybe this is actually a bug in the host Ada compiler used to build
this, which appears to come from the gcc-snapshots package.
--
[armel] gnat-4.4 built from the linaro toolchain fails to build
** Changed in: gcc-linaro
Assignee: (unassigned) = Ulrich Weigand (uweigand)
--
regressions in linaro test build 4.4.4-7ubuntu1~ppa2 compared to 4.4.4-6ubuntu2
https://bugs.launchpad.net/bugs/607635
You received this bug notification because you are a member of Ubuntu
Bugs, which
Looks like this is already fixed in 4.4.4-7ubuntu3.
Closing the Linaro GCC bug as invalid, since the bug was actually in the
testsuite-hardening-fortify.diff patch.
** Changed in: gcc-linaro
Status: Confirmed = Invalid
** Changed in: gcc-linaro
Assignee: Ulrich Weigand (uweigand
Confirmed the build failure and segfault in firefox-3.6.8+build1+nobinonly with
4.4.4-7ubuntu3.
I'm looking into this now.
** Changed in: gcc-linaro
Assignee: (unassigned) = Ulrich Weigand (uweigand)
--
firefox fails to build from source with Linaro toolchain
https://bugs.launchpad.net
Richard Günther agreed to a 4.4 backport. Working on this now.
** Changed in: gcc-linaro
Status: New = In Progress
--
bootstrap failure in stage3 (integer overflow in preprocessor expression)
https://bugs.launchpad.net/bugs/500524
You received this bug notification because you are a
Ok, so the immediate cause of the bug is that a global array is only
4-byte aligned, but the code silently assumes 8-byte alignment.
The problem triggers in jsatom.cpp:js_AtomizeString:
return (JSAtom *) STRING_TO_JSVAL(JSString::unitString(c));
jsapi.h:STRING_TO_JSVAL uses the low
Hmm ... actually there *is* code in the Mozilla sources to attempt to
ensure proper alignment, in jsstr.cpp:
#ifdef __SUNPRO_CC
#pragma pack(8)
#else
#pragma pack(push, 8)
#endif
JSString JSString::unitStringTable[]
#ifdef __GNUC__
__attribute__ ((aligned (8)))
#endif
= {
U(0x00), U(0x01),
Linaro GCC shows this same problem not just on ARM, but also on i386.
So it seems this may now cause problem elsewhere as well ...
--
firefox fails to build from source with Linaro toolchain
https://bugs.launchpad.net/bugs/604874
You received this bug notification because you are a member of
Looks like the culprit may be this patch, which also went upstream. I
checked upstream GCC, and it seems broken on the test case (on all
platforms) as well ...
2009-06-11 Nathan Froyd froy...@codesourcery.com
Backport from upstream:
2009-06-10 Nathan Froyd
The problem is that in cp/decl.c:duplicate_decls, when merging two decls
for one variable, the code uses a memcpy to copy all fields in
tree_decl_common *except* those in tree_common (which are handled
manually). Since the patch moves the user_align and packed_flag bits
from tree_decl_common into
Yes, this does indeed look like the root cause. With the following
patch I'm getting correct behavior back:
--- gcc/cp/decl.c.orig 2010-07-28 19:26:52.0 +0200
+++ gcc/cp/decl.c 2010-07-28 19:28:13.0 +0200
@@ -2068,6 +2068,10 @@
SET_DECL_INIT_PRIORITY (olddecl,
I've committed the fix to the upstream 4.4 branch now. Fix will be in
4.4.5 release.
--
bootstrap failure in stage3 (integer overflow in preprocessor expression)
https://bugs.launchpad.net/bugs/500524
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Opened GCC bugzilla PR c++/45112 to track this now.
** Bug watch added: GCC Bugzilla #45112
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45112
** Also affects: gcc via
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45112
Importance: Unknown
Status: Unknown
--
firefox fails to build
I've looked into the history of the underlying problem a bit more and found out:
- in 4.3 and earlier, the problem didn't yet exist
- in 4.5 and later, the problem is fixed
- however, in 4.4, the problem exists as latent wrong-code generation bug
I've suggested on the gcc-patches list that it
** Changed in: gcc-linaro
Status: Confirmed = Invalid
--
xlpc fails during test with the Linaro GCC
https://bugs.launchpad.net/bugs/607659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It seems the hardening patch was merged upstream in its current form,
and they fixed the VERIFY macro instead.
See http://gcc.gnu.org/ml/gcc-patches/2010-06/msg02690.html for the
patchlet to the VERIFY macro.
--
regressions in linaro test build 4.4.4-7ubuntu1~ppa2 compared to 4.4.4-6ubuntu2
** Changed in: gcc-linaro
Status: New = Confirmed
--
regressions in linaro test build 4.4.4-7ubuntu1~ppa2 compared to 4.4.4-6ubuntu2
https://bugs.launchpad.net/bugs/607635
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: gcc-4.4 (Ubuntu)
Status: New = Confirmed
--
regressions in linaro test build 4.4.4-7ubuntu1~ppa2 compared to 4.4.4-6ubuntu2
https://bugs.launchpad.net/bugs/607635
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've reproduced the problem on i386; the error is:
/home/uweigand/linaro/gcc-4.4-4.4.4/src/libstdc++-v3/testsuite/27_io/objects/char/9661-1.cc:
In function 'bool test01()':^M
/home/uweigand/linaro/gcc-4.4-4.4.4/src/libstdc++-v3/testsuite/27_io/objects/char/9661-1.cc:71:
error: invalid operands of
Public bug reported:
checking for GNU Pth... *** longjmp causes uninitialized stack frame ***:
./conftest terminated
*FAILED*
| Found GNU Pth 2.0.7 under /usr, but
| was unable to perform a sanity execution check. This usually
| means that the GNU Pth shared library libpth.so is present
|
I was unable to investigate much in the original reported scenario,
because the libc.so binary is missing from the tarball:
uweig...@beagle:~$ tar tfz t2-bt-testcase.tar.gz
usr/sbin/rsyslogd-
lib/libz.so.1
lib/libpthread.so.0
lib/libdl.so.2
lib/librt.so.1
lib/libgcc_s.so.1
lib/libc.so.6
91 matches
Mail list logo
