From: Lukasz Wojcik <zbr-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: Devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH] Modification of lexer and parser, improving dtc portability.
Date: Thu, 04 Feb 2010 10:42:27 +0100 [thread overview]
Message-ID: <4B6A9683.300@semihalf.com> (raw)
In-Reply-To: <20100201044601.GA8095@yookeroo>
On 01.02.2010 05:46, David Gibson wrote:
> On Fri, Jan 29, 2010 at 05:31:51PM +0100, Lukasz Wojcik wrote:
>
>> This mod allows successful build of dtc using both bison/flex and
>> yacc/lex.
>>
> Hrm. This will enable dtc to build with both bison and yacc, however,
> it will sacrifice the (much) more useful error messages that
> %locations gives us on bison. So I'm not very happy to do this
> unconditionally.
>
>
Would you be so kind, and possibly point me out where exactly the
differences
between error messages before and after applying this patch lies ? I did
some
testing around dtc being compiled using:
yacc - 1.9 20070509 on Fedora, kernel 2.6.31.5-127.fc12.i686.PAE
and
bison (GNU Bison) 2.4.1, same system.
I was not able to notice any difference. Thanks in advance.
Lukasz.
next prev parent reply other threads:[~2010-02-04 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 16:31 [PATCH] Modification of lexer and parser, improving dtc portability Lukasz Wojcik
[not found] ` <1264782711-52086-1-git-send-email-zbr-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org>
2010-02-01 4:46 ` David Gibson
2010-02-04 9:42 ` Lukasz Wojcik [this message]
[not found] ` <4B6A9683.300-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org>
2010-02-08 8:13 ` David Gibson
2010-02-08 8:13 ` David Gibson
2010-02-08 15:31 ` Jon Loeliger
-- strict thread matches above, loose matches on Subject: below --
2010-01-12 13:57 Lukasz Wojcik
[not found] ` <1263304653-71750-1-git-send-email-zbr-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org>
2010-01-26 23:11 ` David Gibson
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=4B6A9683.300@semihalf.com \
--to=zbr-nyozd4b6jr9wk0htik3j/w@public.gmane.org \
--cc=Devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.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