On Sat, Jun 19, 2021 at 11:10:14AM -0400, Dmitry Goncharov wrote:
> On Sat, Jun 19, 2021 at 10:31 AM Dmitrii Pasechnik
> wrote:
> > It's undefined behaviour in C to point to such a location, isn't it?
> > Is this hack really needed?
>
> There is no hack. It is
On Sat, Jun 19, 2021 at 10:52:41AM -0400, Paul Smith wrote:
> On Sat, 2021-06-19 at 15:31 +0100, Dmitrii Pasechnik wrote:
> > On Fri, Jun 18, 2021 at 12:53:32PM -0400, Paul D. Smith wrote:
> >
> > > Follow-up Comment #1, bug #60798 (project make):
> > > FWIW,
On Fri, Jun 18, 2021 at 12:53:32PM -0400, Paul D. Smith wrote:
> Follow-up Comment #1, bug #60798 (project make):
>
> FWIW, this warning is not valid in this situation. The code is correct; p
> will always be pointing into a valid buffer and never pointing at the first
> character in that buffer,
On Sun, Jun 09, 2019 at 10:11:32PM -0400, Paul Smith wrote:
> On Sun, 2019-06-09 at 18:24 -0400, David A. Wheeler wrote:
> > Proposed solution:
> > By default, make should check the timestamp of the non-.PHONY target(s)
> > produced after
> > executing a rule, and ensure that their timestamps are
On Mon, Apr 02, 2018 at 10:44:53AM -0400, Dennis Clarke wrote:
> On 02/04/18 10:21 AM, Dmitrii Pasechnik wrote:
> > I just wonder whether this is a relatively common case of an updated
> > make dependence, which is incompatible on the binary level (e.g. due to
> > wrong
