This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/55243] STAMP variable is not defined in t-avr
- From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 20 Dec 2012 21:45:11 +0000
- Subject: [Bug target/55243] STAMP variable is not defined in t-avr
- Auto-submitted: auto-generated
- References: <bug-55243-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55243
--- Comment #30 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-12-20 21:45:11 UTC ---
> Almost nothing in GCC was added without precedent: Features were added because
> backend X needed them or frontend Y needed them. To reject an extension just
> because only one target needs it, is not an convincing argument.
I totally disagree of course. You must first try to fit in the existing design
and, only when that fails, you're allowed to propose extensions.
> It's still not known why the ada / gnat stuff rebuilds stuff already there a
> sectons time and at a stage ada / gnat don't expect such a build.
Indeed.
> If I understand correctly, someone familiar with the gnat build machiney and
> philosophy might want to find out why it performs a mistimed rebuild of things
> that are elready supposed to be there?
Yes, that's the crux of the matter.