public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/29639] [4.3 regression] ext/bitmap_allocator/check_allocate_max_size.cc execution test
Date: Sun, 12 Nov 2006 22:08:00 -0000	[thread overview]
Message-ID: <20061112220806.1976.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29639-133@http.gcc.gnu.org/bugzilla/>



------- Comment #49 from ebotcazou at gcc dot gnu dot org  2006-11-12 22:08 -------
Created an attachment (id=12600)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12600&action=view)
Revised linker fix.

Lightly tested on x86.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29639


  parent reply	other threads:[~2006-11-12 22:08 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 23:55 [Bug target/29639] New: FAIL: " pcarlini at suse dot de
2006-10-30  0:02 ` [Bug target/29639] " pinskia at gcc dot gnu dot org
2006-10-30  0:08 ` pcarlini at suse dot de
2006-10-30  0:21 ` pinskia at gcc dot gnu dot org
2006-10-30  0:27 ` pcarlini at suse dot de
2006-10-30  9:57 ` ebotcazou at gcc dot gnu dot org
2006-10-30 11:48 ` pcarlini at suse dot de
2006-10-30 11:53 ` pcarlini at suse dot de
2006-10-30 12:02 ` ebotcazou at gcc dot gnu dot org
2006-10-30 12:05 ` pcarlini at suse dot de
2006-10-30 14:50 ` ebotcazou at gcc dot gnu dot org
2006-10-30 14:50 ` ebotcazou at gcc dot gnu dot org
2006-10-30 14:52 ` [Bug target/29639] [4.3 regression] " ebotcazou at gcc dot gnu dot org
2006-10-30 14:53 ` pcarlini at suse dot de
2006-11-01 12:11 ` bkoz at gcc dot gnu dot org
2006-11-01 12:14 ` ebotcazou at gcc dot gnu dot org
2006-11-02 10:26 ` ebotcazou at gcc dot gnu dot org
2006-11-02 18:41 ` [Bug other/29639] " ebotcazou at gcc dot gnu dot org
2006-11-02 18:44 ` ebotcazou at gcc dot gnu dot org
2006-11-03  0:29 ` pcarlini at suse dot de
2006-11-03 10:46 ` bkoz at gcc dot gnu dot org
2006-11-03 11:28 ` pcarlini at suse dot de
2006-11-03 11:58 ` ebotcazou at gcc dot gnu dot org
2006-11-04  9:29 ` bkoz at gcc dot gnu dot org
2006-11-04 20:17 ` ebotcazou at gcc dot gnu dot org
2006-11-05 19:34 ` danglin at gcc dot gnu dot org
2006-11-05 20:03 ` ebotcazou at gcc dot gnu dot org
2006-11-05 20:15 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-05 21:32 ` ebotcazou at gcc dot gnu dot org
2006-11-06 12:26 ` ebotcazou at gcc dot gnu dot org
2006-11-06 22:03 ` bkoz at gcc dot gnu dot org
2006-11-06 22:06 ` bkoz at gcc dot gnu dot org
2006-11-06 22:15 ` ebotcazou at gcc dot gnu dot org
2006-11-06 23:50 ` bkoz at gcc dot gnu dot org
2006-11-07  0:04 ` ebotcazou at gcc dot gnu dot org
2006-11-07  2:08 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-07 10:03 ` bkoz at gcc dot gnu dot org
2006-11-07 13:10 ` jakub at gcc dot gnu dot org
2006-11-07 15:27 ` bkoz at gcc dot gnu dot org
2006-11-07 17:17 ` ebotcazou at gcc dot gnu dot org
2006-11-07 17:42 ` ebotcazou at gcc dot gnu dot org
2006-11-07 18:27 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-08 11:34 ` bkoz at gcc dot gnu dot org
2006-11-08 11:41 ` ebotcazou at gcc dot gnu dot org
2006-11-08 22:16 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-09 12:33 ` ebotcazou at gcc dot gnu dot org
2006-11-09 12:34 ` ebotcazou at gcc dot gnu dot org
2006-11-10  9:08 ` christian dot joensson at gmail dot com
2006-11-10 15:23 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-12 22:06 ` ebotcazou at gcc dot gnu dot org
2006-11-12 22:08 ` ebotcazou at gcc dot gnu dot org [this message]
2006-11-13  2:01 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-30 19:45 ` chaoyingfu at gcc dot gnu dot org
2006-12-09 19:34 ` danglin at gcc dot gnu dot org
2006-12-09 19:49 ` ebotcazou at gcc dot gnu dot org
2006-12-21 22:10 ` ebotcazou at gcc dot gnu dot org
2006-12-21 22:14 ` ebotcazou at gcc dot gnu dot org

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=20061112220806.1976.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).