public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wvangulik at xs4all dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/33782] FAIL: gcc.c-torture/compile/limits-stringlit.c (test for excess errors) Date: Tue, 06 Nov 2007 20:41:00 -0000 [thread overview] Message-ID: <20071106204146.6063.qmail@sourceware.org> (raw) In-Reply-To: <bug-33782-14721@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from wvangulik at xs4all dot nl 2007-11-06 20:41 ------- Well, that would be ok for the AVR. The test is allocating more than the 64K of adressable space the AVR has. This should be a "expected to fail" for the AVR -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33782
next prev parent reply other threads:[~2007-11-06 20:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-15 15:41 [Bug c/33782] New: [4.3 Regression] " rask at gcc dot gnu dot org 2007-11-06 20:41 ` wvangulik at xs4all dot nl [this message] 2008-04-10 0:00 ` [Bug testsuite/33782] " hutchinsonandy at gcc dot gnu dot org 2008-04-12 15:47 ` hutchinsonandy at gcc dot gnu dot org 2008-05-26 19:59 ` eric dot weddington at atmel 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=20071106204146.6063.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).