public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/21638] [4.1 regression] dce is_gimple_reg_type (type=0x0) building newlib Date: Wed, 18 May 2005 16:01:00 -0000 [thread overview] Message-ID: <20050518160144.20385.qmail@sourceware.org> (raw) In-Reply-To: <20050517233510.21638.hp@gcc.gnu.org> ------- Additional Comments From hp at gcc dot gnu dot org 2005-05-18 16:01 ------- In reply to comment #3: No, I don't think your reading of what rules you refer to is "sane", but then perhaps you're not used to building a unified tree for cross toolchains, re: simtest-howto.html. If you'd done that with any regularity, then you'd have all the bits and would not see newlib as "free code bases to download yourself". I stand by this; I think it can be expected that people test with cross toolchains, for better test coverage than just their "native" machines. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21638
next prev parent reply other threads:[~2005-05-18 16:01 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-17 23:35 [Bug tree-optimization/21638] New: [4.1 regression] cris-elf broken, " hp at gcc dot gnu dot org 2005-05-18 6:12 ` [Bug tree-optimization/21638] " pinskia at gcc dot gnu dot org 2005-05-18 9:09 ` giovannibajo at libero dot it 2005-05-18 9:28 ` hp at gcc dot gnu dot org 2005-05-18 9:34 ` hp at gcc dot gnu dot org 2005-05-18 12:03 ` giovannibajo at libero dot it 2005-05-18 12:11 ` pinskia at gcc dot gnu dot org 2005-05-18 12:34 ` pinskia at gcc dot gnu dot org 2005-05-18 12:36 ` [Bug tree-optimization/21638] [4.1 regression] " pinskia at gcc dot gnu dot org 2005-05-18 16:01 ` hp at gcc dot gnu dot org [this message] 2005-05-18 18:10 ` pinskia at gcc dot gnu dot org 2005-05-18 18:14 ` pinskia at gcc dot gnu dot org 2005-05-18 18:18 ` pinskia at gcc dot gnu dot org 2005-05-18 22:03 ` pinskia at gcc dot gnu dot org 2005-05-19 3:42 ` hp at gcc dot gnu dot org 2005-05-19 10:10 ` [Bug tree-optimization/21638] [4.1 regression] ADDR_EXPR invariancy not recomputed giovannibajo at libero dot it 2005-05-19 14:07 ` hp at bitrange dot com 2005-05-20 9:54 ` giovannibajo at libero dot it 2005-05-24 16:09 ` pinskia at gcc dot gnu dot org 2005-06-05 7:56 ` pinskia 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=20050518160144.20385.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: linkBe 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).