Fixed mainline and 2.38 branch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only on launchpad x86 builders
To manage notifications about this bug
HJ, you likely can reproduce the failue with an asan build of binutils,
or using MALLOC_PERTURB_. I haven't tested the patch yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy
Created attachment 13937
Likely fix
From the backtrace in https://bugs.debian.org/1004269 it is clear that
the problem is triggered by commit e86fc4a5bc37 in which a new extrap
field was added to coffcode.h combined_entry_type but is not used on
anything except rs6000 coff targets.
--
You
Documented
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40214
Title:
ld checks for libs in wrong order. it should be inline with ld.so and
check configured folders first.
To manage
Closing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843479
Title:
gzip in Ubuntu Eoan results in Exec format error on WSL1
To manage notifications about this bug go to:
Well, yes, but patches can be posted to binut...@sourceware.org without
a bugzilla open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843479
Title:
gzip in Ubuntu Eoan results in Exec format
(In reply to Balint Reczey from comment #2)
> Did I miss something?
You did. By subtracting off_adjust from the value written to p_offset
you potentially have p_offset mod page_size != p_vaddr mod page_size.
This will fail the glibc test in elf/dl-load.c resulting in "ELF load
command
It looks to me like your fix ignores the following comment, and will
therefore cause problems with other loaders.
/* We shouldn't need to align the segment on disk since
the segment doesn't need file space, but the gABI
arguably requires the
Fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845190
Title:
binutils nm wrong output format breaks i386 nm work
To manage notifications about this bug go to:
Fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844119
Title:
readelf crash on 32bit, leading to abi-monitor testsuite regression
To manage notifications about this bug go to:
Fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833237
Title:
skiboot ftbfs in eoan
To manage notifications about this bug go to:
This is due to a horrible linker script breaking a new GOT indirect to
GOT relative optimisation (git commit 066f4018ae78).
ld does a preliminary layout to see whether various optimisations can be
done. In this case the preliminary layout indicates that code using a
GOT indirect address can be
It does seem a bit pointless to be building a 32-bit vdso on powerpc64le
where you know there is no 32-bit user runtime.
Now if some other part of the kernel needs to be compiled 32-bit, then it would
appear that gcc will need to be configured with
--enable-targets=powerpcle-linux
It looks like the overlapping FDE error is caused by a bunch of zero
address range FDEs in
/usr/lib/llvm-3.5/lib/libclangCodeGen.a(CGStmtOpenMP.o). These do have
the potential to cause an exception handling problem at runtime, so ld
is correct to complain. (It might also be reasonable for ld to
I don't believe trunk binutils is the source of the problem. Trunk
binutils (commit ae6c7e33 and aa8f4d1e) is merely letting you know about
a case where previous versions of ld silently created binaries with
potential runtime failures during exception handling.
--
You received this bug
Build libOpenCL.so.1 with -Wl,-noinhibit-exec,-Map,libOpenCl.map and
look at the mapfile entries for .eh_frame. Try to match up with
addresses given for the overlapping FDE. This should give you the
object file(s) at fault. My guess is that further analysis will point
at an llvm bug.
--
You
It looks like the overlapping FDE error is caused by a bunch of zero
address range FDEs in
/usr/lib/llvm-3.5/lib/libclangCodeGen.a(CGStmtOpenMP.o). These do have
the potential to cause an exception handling problem at runtime, so ld
is correct to complain. (It might also be reasonable for ld to
I'm looking into moving the section headers to the end of the object
file for ld.bfd. It doesn't look too hard, but there will likely be
some testsuite tweaking needed. It looks like gold puts section headers
last.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch added: patch for subversion-1.8.9
https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1353142/+attachment/4174204/+files/subvers.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Problem reported upstream
http://mail-archives.apache.org/mod_mbox/subversion-dev/201408.mbox/ajax/%3C20140809135509.GC7047%40bubble.grove.modra.org%3E
The bug described in comment #5 has already been fixed upstream
** Changed in: gcc-4.9 (Ubuntu)
Status: New = Invalid
** Changed in:
No, const doesn't make any difference.
On looking again at the source, I've come to the conclusion that this
isn't a vectorizer bug after all. It is simply a coding error.
A compiler is allowed to assume that a pointer to a type is aligned suitably
for the type. So in
*(apr_uint32_t
libsvn_delta/text_delta.c is the problem file causing failure of random-
test. I haven't yet tracked down which function is being miscompiled at
-O3 (or possibly contains a source error exposed by -O3).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Compiling libsvn_delta/text_delta.c with -O2 -ftree-loop-vectorize
-fvect-cost-model=dynamic also causes failure (ie. those two options are
the specific ones added by -O3 that cause failure). The problem is this
code:
/* Copy LEN bytes from SOURCE to TARGET. Unlike memmove() or memcpy(),
*
Huh, looking at that code again, don't we have a bug in the svn source
code? Seems to me that if (target + sizeof(apr_uint32_t) = source)
is the correct condition, not if (end + sizeof(apr_uint32_t) =
target)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I meant
if (source + sizeof(apr_uint32_t) = target)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353142
Title:
subversion tests fail on ppc64el when built with -O3
To manage notifications about
We still have the vectorizer bug though, even after fixing the
condition..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353142
Title:
subversion tests fail on ppc64el when built with -O3
To
Upstream bugzilla with reduced testcase at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62033
** Bug watch added: GCC Bugzilla #62033
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62033
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So the upstream bug was closed as a dup of another bug, 61294. The fix
for that bugzilla was to implement a new -Wmemset-transposed-args, and
remove the memset warning from system headers
(/usr/include/bits/string3.h). However, the glibc side of that fix has
not yet been committed.
The
If LTO was used here I'd say this was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 but that doesn't
appear to be the case from the log.
** Bug watch added: GCC Bugzilla #51744
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744
--
You received this bug notification because you are a
It's not a linker error, and x86_64 mainline gcc 4.10.0 20140727 fails
similarly.
nm bytearraymodel_p.o | grep __warn
U __warn_memset_zero_len
Linking this object file against libc_nonshared.a (which is where this
symbol is defined) generates the linker warning which is turned
This is a stupid testcase, the failure should be ignored.
The glibc values for MINSIGSTKSZ and SIGSTKSZ must be large enough to
cover all known kernels, so that user programs will run on any kernel
and with any usage of vmx, htm and whatever else changes context size.
The values in the kernel on
I'm fairly certain this is a bug in the test itself.
If you take a look at glib2.0/gobject/gmarshal.c
g_cclosure_marshal_VOID__PARAM, you see
typedef void (*GMarshalFunc_VOID__PARAM) (gpointer data1,
gpointer arg_1,
fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/625320
Title:
ld doesn't honor sysroot prefix for ldscripts - track upstream bug
To manage notifications about this bug go to:
More background discussion
http://sourceware.org/ml/binutils/2003-02/msg00449.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/625320
Title:
ld doesn't honor sysroot prefix for ldscripts - track
Fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872687
Title:
c++ -flto always results in unresolved symbols
To manage notifications about this bug go to:
Not a gcc bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778292
Title:
undefined reference to `pow' when building with -flto
To manage notifications about this bug go to:
Yes, this is expected. The PowerPC64 ABI defines function symbols on
their OPD entry, in the .opd section which is part of the data segment.
Thus PowerPC64 functions will be marked as D.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
Found the problem. It's nothing to do with _FORTIFY_SOURCE, and those
intructions indexing off r2 are to do with -fstack-check so no problem
there either.
Fixed as follows. Incidentally this bug was triggered by fixing the
obvious bug in no_global_regs_above
Index: gcc/config/rs6000/rs6000.c
I also couldn't reproduce the problem here with any of the compilers I
have lying around here. davidh, can you attach the .o for your testcase
to this bug report?
--
mountall fails, broken (powerpc?) gcc?
https://bugs.launchpad.net/bugs/43
You received this bug notification because you are
Huh. You have what looks like ppc64 code in there.
4c: 80 02 8f f8 lwz r0,-28680(r2)
50: 90 01 00 3c stw r0,60(r1)
Where did that come from? It seems you have _FORTIFY_SOURCE defined for
you too, somehow. Maybe that is pulling in a bad printf define? Please
attach the
40 matches
Mail list logo
