This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch Makefile.in/Make-lang.in: create bison files atomically
- To: "Zack Weinberg" <zackw at Stanford dot EDU>
- Subject: Re: Patch Makefile.in/Make-lang.in: create bison files atomically
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 15 Oct 2000 19:19:53 -0200
- Cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, gcc-patches at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <200010141821.OAA26526@caip.rutgers.edu><20001014215441.G18277@wolery.stanford.edu>
On Oct 15, 2000, "Zack Weinberg" <zackw@Stanford.EDU> wrote:
> On Sat, Oct 14, 2000 at 02:21:28PM -0400, Kaveh R. Ghazi wrote:
>> Snapshots and releases should provide bison files "in place" to
>> confirm to GNU packaging conventions.
> I don't think this particular bit of the packaging conventions is that
> important
It is. The parser is a very important component of the compiler, and
it should be tested as much as the rest of it. If some future release
of bison ends up generating broken parsers from the GCC .y files, we'd
rather not use them. But the user may just not know about that. So,
for releases, we'd better use the tested generated files, not those
generated by whatever bison happens to be in the users' PATH.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me