public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45261] Doesn't indicate failure status when it doesn't support (attiny2313A)
Date: Wed, 11 Aug 2010 23:20:00 -0000 [thread overview]
Message-ID: <20100811232011.7376.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45261-19554@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from pinskia at gcc dot gnu dot org 2010-08-11 23:20 -------
(In reply to comment #2)
> You're right, the fprintf function should be correct. Moreover, no only the
> attiny2313A is indicated as "result: yes" and is not supported.
What I am trying to say that fprintf function call should be a call to error
which causes the return value of the compiler to change to be 1 instead 0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45261
next prev parent reply other threads:[~2010-08-11 23:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 22:50 [Bug c/45261] New: " rootolini at gmail dot com
2010-08-11 22:55 ` [Bug target/45261] " pinskia at gcc dot gnu dot org
2010-08-11 23:18 ` rootolini at gmail dot com
2010-08-11 23:20 ` pinskia at gcc dot gnu dot org [this message]
2010-08-12 9:54 ` j at uriah dot heep dot sax dot de
[not found] <bug-45261-4@http.gcc.gnu.org/bugzilla/>
2010-11-22 5:00 ` ian.rees at gmail dot com
2010-11-22 7:31 ` ian.rees at gmail dot com
2010-11-22 10:34 ` j at uriah dot heep.sax.de
2010-11-22 16:21 ` ian.rees at gmail dot com
2010-12-15 6:22 ` atstivalet at gmail dot com
2010-12-20 9:19 ` guanx.bac at gmail dot com
2011-01-20 20:15 ` pinskia at gcc dot gnu.org
2011-01-20 20:36 ` pinskia at gcc dot gnu.org
2011-01-20 20:43 ` choudary.omar at gmail dot com
2011-01-24 23:22 ` lars at ibp dot de
2011-02-26 19:36 ` brawrf at gmail dot com
2011-02-27 13:13 ` denisc at gcc dot gnu.org
2011-02-28 17:37 ` denisc at gcc dot gnu.org
2011-04-14 15:21 ` gjl at gcc dot gnu.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=20100811232011.7376.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).