public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/44752] insn-automata.c: empty translation unit
Date: Mon, 05 Jul 2010 20:15:00 -0000 [thread overview]
Message-ID: <20100705201457.32379.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44752-5394@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from amylaar at gcc dot gnu dot org 2010-07-05 20:14 -------
(In reply to comment #5)
> Created an attachment (id=21088)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21088&action=view) [edit]
> patch which needs testing
>
> I have not tested this fix but it should work and should remove the
> warning/error for these targets.
No, the translation unit is still considered empty.
You have to put something syntactic into it, although it could be an
extern declaration, an static inline function, or a struct declaration, e.g.:
struct rtx_def;
--
amylaar at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2010-07-05 01:33:44 |2010-07-05 20:14:57
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44752
next prev parent reply other threads:[~2010-07-05 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 15:54 [Bug target/44752] New: crx-elf " amylaar at gcc dot gnu dot org
2010-07-01 15:59 ` [Bug rtl-optimization/44752] " amylaar at gcc dot gnu dot org
2010-07-01 21:36 ` manu at gcc dot gnu dot org
2010-07-01 22:40 ` amylaar at gcc dot gnu dot org
2010-07-01 22:52 ` manu at gcc dot gnu dot org
2010-07-05 1:33 ` pinskia at gcc dot gnu dot org
2010-07-05 1:35 ` pinskia at gcc dot gnu dot org
2010-07-05 20:15 ` amylaar at gcc dot gnu dot org [this message]
2010-07-12 17:17 ` amylaar at gcc dot gnu dot org
2010-07-12 19:51 ` amylaar 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=20100705201457.32379.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).