public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "developer at sandoe-acoustics dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/43061] 47 new GCC HEAD@156527 regressions
Date: Mon, 15 Feb 2010 23:10:00 -0000	[thread overview]
Message-ID: <20100215231041.1686.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43061-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #29 from developer at sandoe-acoustics dot co dot uk  2010-02-15 23:10 -------
Created an attachment (id=19884)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19884&action=view)
attach "used" attribute as well as marking vars used.

Jakub's comment seems to do the trick - thanks.
I've applied a "used" attribute in the same place that the TREE_USED is placed.


-- 


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


  parent reply	other threads:[~2010-02-15 23:10 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 13:03 [Bug objc/43061] New: " dominiq at lps dot ens dot fr
2010-02-14 13:46 ` [Bug objc/43061] " developer at sandoe-acoustics dot co dot uk
2010-02-14 15:25 ` rguenth at gcc dot gnu dot org
2010-02-14 16:05 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 16:28 ` rguenth at gcc dot gnu dot org
2010-02-14 16:33 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 16:33 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 16:45 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 17:44 ` rguenth at gcc dot gnu dot org
2010-02-14 18:50 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 19:00 ` rguenth at gcc dot gnu dot org
2010-02-14 19:02 ` rguenth at gcc dot gnu dot org
2010-02-14 19:07 ` pinskia at gcc dot gnu dot org
2010-02-14 21:13 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 21:29 ` rguenth at gcc dot gnu dot org
2010-02-14 21:53 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 21:56 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 21:56 ` rguenth at gcc dot gnu dot org
2010-02-14 22:12 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 22:16 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 22:25 ` rguenth at gcc dot gnu dot org
2010-02-14 23:22 ` developer at sandoe-acoustics dot co dot uk
2010-02-14 23:27 ` rguenth at gcc dot gnu dot org
2010-02-14 23:57 ` developer at sandoe-acoustics dot co dot uk
2010-02-15 17:38 ` mikestump at comcast dot net
2010-02-15 19:54 ` developer at sandoe-acoustics dot co dot uk
2010-02-15 21:09 ` jakub at gcc dot gnu dot org
2010-02-15 21:52 ` developer at sandoe-acoustics dot co dot uk
2010-02-15 22:37 ` jakub at gcc dot gnu dot org
2010-02-15 23:10 ` developer at sandoe-acoustics dot co dot uk [this message]
2010-02-16  9:23 ` developer at sandoe-acoustics dot co dot uk
2010-02-16 10:06 ` jakub at gcc dot gnu dot org
2010-02-16 10:14 ` rguenth at gcc dot gnu dot org
2010-02-16 10:15 ` rguenth at gcc dot gnu dot org
2010-02-16 14:58 ` developer at sandoe-acoustics dot co dot uk
2010-02-16 16:25 ` mikestump at comcast dot net
2010-02-18 22:06 ` mikestump at comcast dot net
2010-02-19  8:44 ` developer at sandoe-acoustics dot co dot uk
2010-02-19 19:07 ` mrs at gcc dot gnu dot org
2010-02-19 19:15 ` mikestump at comcast dot net
2010-02-19 23:28 ` developer at sandoe-acoustics dot co dot uk
2010-02-21 12:46 ` dominiq at lps dot ens dot fr

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