Control: severity 1061370 grave
Control: forcemerge -1 1061370
Matthias Klose [2024-02-01 8:30 +0100]:
> please don't file duplicate reports, see #1061370
Ah, sorry -- it wasn't clear from the title that it was about this problem, nor
was it RC. Marking a duplicate, so that it's easier to find.
t-checked a few of the autopkgtest regressions on the PTS [3], and they
all failed on the exact same issue, e.g. [4].
Thanks!
Martin
[1]
https://buildd.debian.org/status/fetch.php?pkg=cockpit&arch=armel&ver=310-1&stamp=1706722995&raw=0
[2]
https://buildd.debian.org/status/fetch.php?
On Mon, Mar 14, 2022 at 4:45 PM Martin-Éric Racine
wrote:
>
> On Mon, Mar 14, 2022 at 4:39 PM Marc Haber
> wrote:
> >
> > On Mon, Mar 14, 2022 at 04:32:58PM +0200, Martin-Éric Racine wrote:
> > > On Mon, Mar 14, 2022 at 4:30 PM Marc Haber
> > > wrote:
>
On Mon, Mar 14, 2022 at 4:39 PM Marc Haber
wrote:
>
> On Mon, Mar 14, 2022 at 04:32:58PM +0200, Martin-Éric Racine wrote:
> > On Mon, Mar 14, 2022 at 4:30 PM Marc Haber
> > wrote:
> > >
> > > On Mon, Mar 14, 2022 at 04:23:40PM +0200, Martin-Éric Racine
Greetings,
As I just noticed, 'netstat' similarily dumps core on the Geode LX host.
Martin-Éric
. Attempts to build
from source on the Geode LX host itself, to test for possible autotool issues,
crashes early during the build. Logs attached.
Martin-Éric
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500,
Minimal test case for armel:
# cat BUG.c
extern _Complex float g(int N, int dims[N]);
void f(void)
{
int dims[1];
_Complex float val = g(1, dims);
}
# arm-linux-gnueabi-gcc --version
arm-linux-gnueabi-gcc (Debian 11.2.0-9) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
/med-team/bart/-/jobs/2121098
I recently filed an upstream bug for a problem which
may also be related (but affects x86_64):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103770
Best,
Martin
> On Mon, 06 Sep 2021 at 09:48:00 +0300, Martin-Éric Racine wrote:
> >Message: Process 838 (tracker-extract) of user 1000 dumped core.
> >
> > Stack trace of thread 838:
> > #0 0xb1009f90 n/a (libexiv2.so.27 + 0x74f90)
>
la 28. elok. 2021 klo 13.43 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> la 28. elok. 2021 klo 13.40 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
> >
> > On 2021-08-28 13:36, Martin-Éric Racine wrote:
> > > la 28. elok. 2021 klo 12.58 Aurelien
la 28. elok. 2021 klo 13.40 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
>
> On 2021-08-28 13:36, Martin-Éric Racine wrote:
> > la 28. elok. 2021 klo 12.58 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
> > > > $ sudo coredumpctl debug 1011
> > >
.0.a200afe0e5134b8a812b05c898c8b859.2083.163014678500.zst
Message: Process 2083 (apt-get) of user 0 dumped core.
Stack trace of thread 2083:
#0 0xb7ae9170 frame_dummy (libstdc++.so.6 + 0x87170)
gdb terminated by signal ILL.
Martin-Éric
pe 30. lokak. 2020 klo 13.50 Simon McVittie (s...@debian.org) kirjoitti:
> On Fri, 30 Oct 2020 at 10:35:21 +0200, Martin-Éric Racine wrote:
> > [ 165.903916] traps: gnome-shell[869] trap invalid opcode ip:b5518f8a
> > sp:b17d6d80 error:0 in libmozjs-78.so.78.3.0[b4b98000+98
Package: g++-8
Version: 8.3.0-6
Severity: important
Dear Maintainer,
* What led up to the situation?
Using std::filesystem::directory_iterator in a C++17 program.
* What exactly did you do (or not do) that was effective (or ineffective)?
Attempt to compile and link the program.
Originally I w
Package: g++-8
Version: 8.3.0-6
Severity: important
Dear Maintainer,
* What led up to the situation?
Using std::filesystem::directory_iterator in a C++17 program.
* What exactly did you do (or not do) that was effective (or ineffective)?
Compile and link the program.
Originally I was trying t
Quoting Uwe Kleine-König :
If the concerns are mostly about the hardware not being rackable, there
is a rackable NAS by Netgear:
https://www.netgear.com/business/products/storage/readynas/RN2120.aspx#tab-techspecs
This seems to be out of stock and discontinued, unfortunately.
Anyway,
* Roland Stigge [2016-01-25 16:53]:
> Hi Martin!
>
> numberOfColors is declared as "const unsigned short", and also defined
> correctly, as far as I can see.
>
> Therefore, I'm assuming a GCC bug here?
Copying doko.
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
https://whatofhow.wordpress.com/2016/01/20/gcc-6/
Thanks for tracking that down! Let's reassign the bug against gcc-6.
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
* Martin Michlmayr [2016-01-13 23:15]:
> If you think it would be useful, I should be able to find time within
> the next 10 days to do a build of Debian unstable on amd64 and
> probably on arm64.
I completed the rebuild of Debian unstable with GCC 6 and reported 520
build failures t
> That is a fully legal C construct. I cannot see why gcc6 is throwing an
> error here.
>
> That seems a bug in gcc6 for me. See also [0].
doko?
> [0] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68979
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
Package: gcc-6
Version: 6-20160117-1
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69328
With dpkg-buildflags set to -O3
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
..
> Package: samtools-legacy
> Version: 0.1.19-2
...
> gcc -c -g -O2 -fstack-protector-strong -W
Package: gcc-6
Version: 6-20160117-1
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69421
With dpkg-buildflags set to -O3
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> Package: octave
> Version: 4.0.0-5
...
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I
Package: gcc-6
Version: 6-20160117-1
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69328
With dpkg-buildflags set to -O3 (although I believe doko saw it with
normal flags on powerpc).
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> Package: bochs
> Version: 2.
pped.
> >I can reproduce it now. How do I generate a testcase for an LTO bug?
>
> https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction#Reducing_LTO_bugs
I thought I got further but then I got stuck. I hopened a bug
upstream and asked for help.
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
198
> 0x663210 cp_parser_expression_statement
> ../../src/gcc/cp/parser.c:10659
> 0x6516d4 cp_parser_statement
> ../../src/gcc/cp/parser.c:10510
> 0x6524d1 cp_parser_statement_seq_opt
> ../../src/gcc/cp/parser.c:10782
> Please submit a full bug report,
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
r: in dwarf2out_finish, at dwarf2out.c:27175
> 0x6a2e00 dwarf2out_finish
> ../../src/gcc/dwarf2out.c:27175
> Please submit a full bug report,
> with preprocessed source if appropriate.
> Please include the complete backtrace with any bug report.
> See for instructions.
> lt
Package: gcc-6
Version: 6-20160117-1
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69166
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> Package: euler
> Version: 1.61.0-10
...
> gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/gtk-2.0
> -I/usr/lib/x86_64-linu
Package: gcc-6
Version: 6-20160117-1
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69241
internal compiler error: in assign_temp, at function.c:961
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> Package: opencv
> Version: 2.4.9.1+dfsg-1.2
> [ 12%] Building CXX ob
Ubuntu test rebuild on the
> Debian packages. Of course there will be some false positives.
If you think it would be useful, I should be able to find time within
the next 10 days to do a build of Debian unstable on amd64 and
probably on arm64.
--
Martin Michlmayr
http://www.cyrius.com/
* Matthias Klose [2015-06-08 03:20]:
> could you attach the preprocessed source together with the options
> to trigger this ICE? and maybe ask the ARM porters for help.
I'm looking into it.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debi
On Wed, Sep 03, 2014 at 02:37:48PM +0200, Matthias Klose wrote:
>
> please recheck with the current version and the gcc-snapshot package in
> unstable
> and -ffat-lto-objects
Sorry for the delay, I fail to find the time to grab the simgrid
package on a non-AMD architecture, comment the line "lto
Package: libgcj15
Version: 4.9.1-1
Severity: normal
$ adequate libgcj15
Reports that:
libgcj15:i386: broken-symlink
/usr/lib/jvm/java-1.5.0-gcj-4.9-i386/jre/lib/security/java.security ->
/etc/security/classpath.security
-- System Information:
Debian Release: jessie/sid
APT prefers testing
Since I had no idea of where the problem could come from, I tried to
simplify it a bit, and removed the static library that we use (*) so
that I can switch back to regular ar and ranlib.
But the bug did not disapear in the move, it still occured on powerpc
this time:
https://buildd.debian.org/st
Package: gcc-4.9
Version: 4.9.0-6
Severity: normal
Dear Maintainer,
since 4.9, the simgrid package sometimes FTBFS with the following
error on various architectures:
lto1: fatal error: LTO_tags out of range: Range is 0 to 368, value is 756
This may be related to the fact that we build with gcc
double. Subsequent rounding to float then rounds up giving 0x1p+1f.
Cheers,
- Martin
/*
** gcc does not seem to handle (single precision) floating point constants correctly.
** I believe the closest single precision floating point number to:
** 1.999403953553f
** is
** 0x1.fep+0
** which
to a double precision float and
then round it back to a single precision float, giving a double rounding
bug. The attached code demonstrates the discrepancy with strtof. The
fix will likely be making sure that float literals are parsed as floats
not doubles.
Cheers,
- Martin
/*
** gcc does not
4.7.0-5
GCC, the GNU Compiler Collection
(base package)
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with
The symlink to libstdc++.so is faulty and can be fixed with:
sudo ln -sf /usr/lib/libstdc++.so.6 /usr/lib/gcc/x86_64-linux-gnu/4.4.5
/libstdc++.so
Hope this helps. But it is a bug indeed.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
Package: src:gcj-4.6
Version: 4.6.1-2
Severity: wishlist
Tags: patch
Dear Maintainer,
reviewing the translated German package description I found some spelling
errors for GCJ and GCC which upstream itself writes in capitals.
The attached patch will fix it.
Kind regards
Martin
On 2 March 2011 02:34, Matthias Klose wrote:
> armel (although optimized for a different processor)
Hi
For which processor (/architecture) is it optimized, and do you mean
optimized-for, or only-runs-on?
I ask in case this would mean dumping all the armv4t systems that are
using Debian armel.
A patch has turned up for glibc-2.9. I'm trying it on eglibc-2.10...
See http://sourceware.org/ml/crossgcc/2009-11/msg8.html
--- glibc-ports-2.9/sysdeps/arm/dl-machine.h.orig 2009-11-03
22:03:57.0 +0100
+++ glibc-ports-2.9/sysdeps/arm/dl-machine.h2009-11-03 22:11:45.0
this does not work. do i need to include
another header file before sstream or do i need some specific compiler
option or something?
regards
martin
--
"A Catholic is more capable of evil than anyone"
Graham Greene
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
wi
fixed 528587 4.4.1-1
thanks
* Mark de Wever [2009-09-15 22:13]:
> On Fri, May 15, 2009 at 11:16:22AM +0200, Martin Michlmayr wrote:
> > The GCC folks told me that this is a compiler bug. Sorry for wasting
> > your time.
>
> I saw this bug is still open, but the bug has
"brian m. carlson" writes:
> I'm aware of that. My opinion remains the same: GCC should generate
> POSIX-conformant code without warnings with -O2 -Wall. That can be
> achieved by disabling -fstrict-aliasing at -O2, by patching glibc to
> allow aliasing of the relevant types, by special-casing
"brian m. carlson" writes:
> I expect that when used on a POSIX system (at least in strict POSIX mode
> or when invoked as "c99"), gcc-4.4 neither warns nor generates code
> contrary to POSIX with -O2 -Wall.
You can add -fno-strict-aliasing which will disable the optimisation
and thus prevent th
"brian m. carlson" writes:
> This is a standard and idiomatic usage of Berkeley sockets. AFAIK,
> there is no other way to work with the sockets interface, and even if
> there were, this method is extremely common, not to mention sanctioned
> by POSIX.
It may be idiomatic but it's not strictly
This is presumably #528768 (i.e. a bug in libgmp3c2 on powerpc).
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
..4.3-2009-02-23-r144380/gcc] ./g++ -v
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: /home/tbm/scratch/gcc-4.3/configure --disable-bootstrap
--enable-languages=c,c++
Thread model: posix
gcc version 4.3.4 20090223 (prerelease) (GCC)
--
Martin Michlmayr
http://www.cyrius
* Rutger ter Borg [2009-02-23 12:14]:
> Package: g++ (Debian 4.3.3-4) 4.3.3
>
> The current c++ compiler segfaults on the following simple code mistake,
> where
> a destructor doesn't have the same id as that the class.
Confirmed. Note that this didn't happe
ioning
to treat misalignment.
t.c:11: note: cost model: Adding cost of checks for loop versioning
aliasing."
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
forwarded 512050 http://gcc.gnu.org/PR38899
thanks
* brian m. carlson [2009-01-17 17:13]:
> I believe that it's the maintainers job to file the bug upstream, and
OK, I've verified that 4.3 and 4.4 from SVN produce the same code.
--
Martin Michlmayr
http://www.cyrius.com/
--
T
Package: g++-4.3
Version: 4.3.2-1.1
When compiling a program which used the C++ STL to contain instances of a class
of my own devising, I encountered spurious warnings. I have been able to reduce
the necessary code to a simple test case, which is included in this bug report
along with a transcript
* brian m. carlson [2009-01-16 18:38]:
> Obviously, since the two functions do the exact same thing, they should
> be optimized to be identical. Instead, mul is pessimized.
Can you check if this happens with gcc-4.3 and trunk from SVN, and if
so, file the bug upstream?
--
Martin Mic
86_64-2.5/tmp/python2.5-2.5.3/Modules/datetimemodule.o
> /tmp/python2.5-2.5.3/Modules/datetimemodule.c: In function
> 'datetime_gettimetz':
> /tmp/python2.5-2.5.3/Modules/datetimemodule.c:4395: internal compiler error:
> in insert_into_preds_of_block, at tree-ssa-pre.c:3131
This
I have a new email address!You can now email me at: mar_tinden...@ymail.com
Sir/Madam,
Ive business to discuss with you, please contact me, for more details
Dent
- Martin Dent
wing code:
Thanks, I can confirm this with gcc 4.2, 4.3 and 4.4.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
t that's how it is...
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
p? :-)
You could confirm how much RAM the machine has... but I guess it's
clear that it doesn't have terribly much and that the compiler simply
ran out of RAM.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with
forwarded 487406 http://gcc.gnu.org/PR38642
thanks
* Enrico Zini [2008-06-24 09:27]:
> > is this arm only, or armel as well?
>
> ARM only.
Thanks, I can confirm this with gcc 4.3 and 4.4 from SVN.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to deb
1.1-1 that failed on the build machine is the same
1.1-1 that I just obtained from the mirrors.
Or do I need to do anything special to see this compiler error?
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsub
s=raw
This error typically indicates that GCC ran out of memory. I'm not
sure how much RAM the build machine (modi) has, but I guess not
enough... Martin: who runs modi and how much RAM does it have?
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian
* Martin Zobel-Helas [2008-12-26 12:47]:
> > > g++: Internal error: Killed (program cc1plus)
> >
> > This error typically indicates that GCC ran out of memory. I'm not
> > sure how much RAM the build machine (modi) has, but I guess not
> > enough... Marti
ystem.
Do you still see this?
I should also note that a cvxopt arm binary exists in the archive,
although I've no idea who built it (or how it was built).
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subje
Hi,
On Fri Dec 26, 2008 at 12:42:34 +0100, Martin Michlmayr wrote:
> * Eugen Dedu [2008-11-17 19:43]:
> > g++: Internal error: Killed (program cc1plus)
> > Please submit a full bug report.
> > See for instructions.
> >
> > http://experimental.debian.net/fet
* Michael Buesch [2008-12-12 23:26]:
> The .i file is attached anyway.
>
> Do you need more information?
Thanks, that's exactly what we needed. I forwarded it as
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38553
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, e
There are also about 20 build errors because of improved preprocessor
checks, as described at
http://www.cyrius.com/journal/gcc/gcc-4.4-preprocessor-errors
I'll try to do another archive build when the gcc-4.4 package is in
Debian.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNS
Package: gfortran-4.3-doc
Version: 4.3.0.nf1-1
Severity: normal
According to the html manual, the intrinsic function SIGN(A,B) gives
ABS(A) if B\ge 0.
In gfortran-4.3 there is a difference between +0.0 and -0.0. This should
be mentioned in the documentation.
program t
a=0.0
ce_try_sign_mask (ifcvt.c): b_unconditional
- gdc-4.1
- gdc-4.2
- prima
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Confirmed - there is a misaligned word access in the test case
# echo 5 > /proc/cpu/alignnment
$ gcc foo.c
$ ./a.out
Bus error
reproducible in arm-sid using old-abi or eabi-oldabi-compat kernels.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [
On 6/24/08, Matthias Klose <[EMAIL PROTECTED]> wrote:
> Is this arm only, or armel as well?
armel too.
I have /proc/cpu/alignment set to 5 and it's doing an unaligned word access
under gdb (and gcc -g):
Program received signal SIGBUS, Bus error.
0x400d2cd0 in std::string::assign () from /usr/li
On Sun, Apr 27, 2008 at 04:17:04PM +0200, Matthias Klose wrote:
> tag 473647 + wontfix
> thanks
>
> - well, how long should a compiler be kept as a legacy compiler?
> - set the package on hold if you upgrade, and the package is kept
>installed (or install it from etch).
> - having libg2c0 o
* Grant Grundler <[EMAIL PROTECTED]> [2008-04-19 19:08]:
> This is a good idea - switch to gcc-4.3 for everything but the kernel.
> I didnt think this would be possible but I'm not sure why I thought that.
We use gcc-4.1 for the kernel anyway, rather than the default
com
On 4/4/08, Matthias Klose <[EMAIL PROTECTED]> wrote:
> Martin Guy writes:
> > ...and on i386-sid on Athlon-32 the testsuite fails mightily:
> >
> > === libffi Summary ===
> >
> > # of expected passes505
> > # of unexpe
...and on i386-sid on Athlon-32 the testsuite fails mightily:
=== libffi Summary ===
# of expected passes505
# of unexpected failures513
# of unresolved testcases 8
# of unsupported tests 15
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Package: libffi
Version: 3.0.4-2
There are testsuite failures when building on ARM (which are then ignored...)
Running /home/martin/arm/arma/libffi-3.0.4/testsuite/libffi.call/call.exp ...
FAIL: libffi.call/cls_2byte.c -O0 -W -Wall execution test
FAIL: libffi.call/cls_3_1byte.c -O0 -W -Wall
s-static-sjlj'
make[6]: *** [rts-static-sjlj/libgnat.a] Error 2
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ds on arm.
Either -fstack-protector should be fixed in gcc, or it should be
disabled on arm/armel, so that it is solved for all packages in the
archive, not just for cupsys.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)
* Martin Michlmayr <[EMAIL PROTECTED]> [2008-01-21 18:33]:
> > This address looks highly suspicious as it is not aligned while the type
> > is a (void*).
> >
> > On ARM unaligned access are not guaranteed to work and actually
> > depends on the CPU. On som
Hi again,
Martin Pitt [2008-03-16 13:27 +0100]:
> Hardcoding such exceptions into all source packages is EBW. cupsys
> runs a proper configure test whether -fstack-protector works, which
> apparently succeeds on arm.
>
> Either -fstack-protector should be fixed in gcc, or it shoul
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2008-02-27 15:10]:
> The following code causes ICE on g++-4.1/4.2/4.3 :
Sounds a lot like http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35109
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
r an upload of gcc-4.3 is made with this fix. Is this correct?
Right, or you work around the GCC bug by lowering the -O level on
Alpha. But I'd just wait for gcc-4.2/gcc-4.3 to be updated in Debian.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTE
he good news is that this bug has been
fixed upstream, so all you need is for doko to upload a new gcc-4.2
package.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
irtual void
> c_unparser::visit_foreach_loop(foreach_loop*)':
> translate.cxx:2496: internal compiler error: in clear_marks, at
> ggc-page.c:1621
I cannot reproduce this ICE.
--
Martin Michlmayr
http://www.cyrius.com/
d this bug only after there was
a big discussion with the consensus that these messages would be
errors in 4.3, but recently there was yet another discussion with
a different outcome.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of &q
pt nichts
sagen, weil ich Sidux gar nicht kenne. Du solltest Dich daher am besten an
die entsprechenden Support-Seiten Deiner Distribution wenden, die koennen
sicher besser weiterhelfen.
Gruss
Martin Preuss
--
"Things are only impossible until they're not"
Martin Preuss - http
I forwarded this.
Note that (the still unreleased) 4.3 works.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
x27;s not even part of unstable
yet (i.e. they have their own separate archive).
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
* Camm Maguire <[EMAIL PROTECTED]> [2008-01-02 16:55]:
> Is EABI the old arm, or the new? Couldn't this make a difference?
I can reproduce the problem with the old ABI (i.e. the current port in
Debian). I'll open a bug report with GCC.
--
Martin Michlmayr
http://www.cy
* Camm Maguire <[EMAIL PROTECTED]> [2008-01-02 16:55]:
> Is EABI the old arm, or the new? Couldn't this make a difference?
EABI is the new ABI.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
NU C Library:
> Shared libraries
>
> no segfaults here... :-/
I get
./t(sid)[EMAIL PROTECTED]:~$ ./t2
0x18be8ebb
(nil)
on a box with EABI kernel an old ABI chroot. I see the segfault on
leisner (the box Camm probably used).
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBS
4.2.2-4 The GNU C preprocessor
> ii gcc-4.2-base4.2.2-4 The GNU Compiler Collection
> (base
> ii libc6 2.7-2GNU C Library: Shared libraries
> ii libgcc1 1:4.2.2-4GCC support library
> ii li
I just tried foo.c on up-to-date arm-sid and armel-sid systems, both
under qemu and on real hardware and I cannot reproduce the problem;
all succeed the same way, for example:
[EMAIL PROTECTED]:~$ /usr/bin/gcc-4.2 foo.c
[EMAIL PROTECTED]:~$ ./a.out
0xbe92ec84
0x1
0x2
0x3
[EMAIL PROTECTED]:~$ gcc -
e still have
> several of those in use.
I just tried on a Netwinder and I can successfully compile that source
file there too. Do those segfaults happen on all Netwinder buildds
or only on elara?
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SessMgr::Session&,
> nemiver::common::Transaction&)':
> nmv-sess-mgr.cc:343: internal compiler error: Segmentation fault
Works fine here. I think the package should be retried on ARM.
--
Martin Michlmayr
http://www.cyrius.com/
nal compiler error: in
> delete_output_reload, at reload1.c:7958
This was fixed in SVN about 2 weeks ago.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
if I hadn't changed optimization.
(Looking at my logs, it seems shogun failed with "multiple parameters
named 'posweights_lhs'", but apparently I didn't file a bug report.
I'll try to send a bug report tomorrow.)
--
Martin Michlmayr
http://www.cyrius.com/
--
e but not with
4.1.2-18 from testing/unstable. So I think this has been fixed
upstream (it might be PR30286 but I'm not sure).
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
print_raw.c -fPIC -DPIC -o .libs/print_raw.o
Can you add --save-temps to that call and send the resulting .i file.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
r: in
iv_analyze_expr, at loop-iv.c:935
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 452811 + upstream
forwarded 452811 http://gcc.gnu.org/PR34493
thanks
* Nacho Barrientos Arias <[EMAIL PROTECTED]> [2007-11-25 12:41]:
> gcc-4.2 (and others) dies building sks-ecc[0] on powerpc in the
> following situations.
Thanks for the testcase.
--
Martin Mi
1 - 100 of 794 matches
Mail list logo
