public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16625] Discarded Linkonce sections in .rodata
Date: Tue, 23 Nov 2004 16:40:00 -0000 [thread overview]
Message-ID: <20041123164003.24398.qmail@sourceware.org> (raw)
In-Reply-To: <20040719105906.16625.wenzel@tu-harburg.de>
------- Additional Comments From hjl at lucon dot org 2004-11-23 16:40 -------
Please try the Linux binutils 2.15.94.0.1.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16625
next prev parent reply other threads:[~2004-11-23 16:40 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 10:59 [Bug c++/16625] New: " wenzel at tu-harburg dot de
2004-07-19 10:59 ` [Bug c++/16625] " wenzel at tu-harburg dot de
2004-07-19 13:40 ` hjl at lucon dot org
2004-07-19 17:57 ` pinskia at gcc dot gnu dot org
2004-08-01 9:31 ` schwab at suse dot de
2004-08-01 9:33 ` schwab at suse dot de
2004-08-01 15:10 ` giovannibajo at libero dot it
2004-08-01 16:16 ` hjl at lucon dot org
2004-08-07 16:41 ` hjl at lucon dot org
2004-08-25 7:33 ` andrew at walrond dot org
2004-08-27 11:34 ` andrew at walrond dot org
2004-11-17 16:59 ` gustavo dot boiko at kdemail dot net
2004-11-23 9:19 ` trapni at gentoo dot org
2004-11-23 16:40 ` hjl at lucon dot org [this message]
2004-11-24 2:59 ` trapni at gentoo dot org
2004-11-24 3:19 ` trapni at gentoo dot org
2004-11-24 7:01 ` hjl at lucon dot org
2004-11-24 7:35 ` trapni at gentoo dot org
2004-11-24 14:38 ` hjl at lucon dot org
2004-12-09 17:54 ` brian dot morey at atk dot com
2005-06-27 14:31 ` marc dot price at rd dot bbc dot co dot uk
2005-08-30 8:58 ` markus dot glaser at daimlerchrysler dot com
[not found] <bug-16625-8878@http.gcc.gnu.org/bugzilla/>
2005-10-25 11:46 ` hidden_peak at mail dot ru
2005-11-18 18:19 ` dank at kegel dot com
2005-12-30 10:24 ` pluto at agmk dot net
2005-12-30 13:08 ` karol at mikronika dot com dot pl
2005-12-30 13:30 ` karol at mikronika dot com dot pl
2006-04-04 9:01 ` karol at mikronika dot com dot pl
2006-05-02 21:02 ` simon_baldwin at yahoo dot com
2006-05-11 16:12 ` perry at kundert dot ca
2006-05-11 16:16 ` pinskia at gcc dot gnu dot org
2006-05-12 13:41 ` karol at mikronika dot com dot pl
2006-09-22 16:57 ` kai dot engert at gmx dot de
2006-10-02 20:16 ` hacksaw at hacksaw dot org
2006-12-29 17:40 ` pfaff at mcmaster dot ca
2007-03-02 16:25 ` michael dot klein at fazi dot de
2007-03-02 19:43 ` hjl at lucon dot org
2007-03-05 8:43 ` michael dot klein at fazi dot de
2007-03-05 14:20 ` hjl at lucon dot org
2007-03-05 14:53 ` hidden_peak at mail dot ru
2007-03-05 15:26 ` hjl at lucon dot org
2007-03-05 16:21 ` michael dot klein at fazi dot de
2007-03-05 16:38 ` hjl at lucon dot org
2007-03-06 12:08 ` michael dot klein at fazi dot de
2007-03-06 15:27 ` hjl at lucon dot org
2007-03-06 16:33 ` michael dot klein at fazi dot de
2007-03-07 10:14 ` michael dot klein at fazi dot de
2007-03-07 10:20 ` michael dot klein at fazi dot de
2007-03-07 14:33 ` hjl at lucon dot org
2007-04-25 17:16 ` zhong dot xie at yahoo dot ca
2007-09-07 7:09 ` ebotcazou at gcc dot gnu dot org
2010-04-03 18:18 ` tg at mirbsd dot org
[not found] <bug-16625-4@http.gcc.gnu.org/bugzilla/>
2012-05-11 1:34 ` h.seki.95 at azbil dot com
2012-05-11 3:37 ` h.seki.95 at azbil dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041123164003.24398.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).