Hi, sure. I've added a `bison_20180901` _ref_ at my VCS backups provider:
https://github.com/galegosimpatico/amara/tree/bison_20180901 At that branch my macOS computer is able to reproduce what I just wrote to you only by ordering `make` (I verified with a clean clone). Note that the dependent project is not free software ATTOW. Now I'm going to use that branch to prune out the reduced example I understand I’m supposed to provide you. If I succeed, or whenever I give up reducing, I’ll create some other repository, license it BSD0, and copy my reduced example over there. Then I'll try to transform the snippet (or collection of snippets, I’m afraid) into a text I can mail to bug-bi...@gnu.org, and come back to submit there a report with a reduced example, my expectation, my result, and convenient links to any free software resources I shall consider. I hope all of this will be enough compliant with your etiquette (which I'm not familiar with), and in any case you already have (if that helps) an open source not reduced example. Thank you. Truly best cheers and regards! > On 1 Sep 2018, at 11:54, akim <a...@lrde.epita.fr> wrote: > > Le 2018-08-30 07:47, uxio prego a écrit : > > Hi! > >> Dear maintainer, >> I bet you already know that Bison... 2.7 up to... 3.1 I think? >> Can output a PREFIX.tab.c doc so that when compiled by >> LLVM 9 a security warning (see `man 3 printf`) gets >> emitted. > > No, I am not aware of this. Please, make a complete bug report, > with some example, what you expect, and what you get instead. > > >> I don't know much about LLVM, but I think they claim to be >> GCC compatible. > > This should be irrelevant for Bison, which aims at the C standard. > > >> Does Bison in any way claim to be LLVM compatible? >> Were you aware of such LLVM alerts? Do you want me to >> share my compiler warnings? > > Yes please! > > > Cheers! _______________________________________________ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
