[PATCH] Check .exe as well when a target does not exist on OS/2

2023-01-13 Thread KO Myung-Hun
For example, foo: foo.c gcc $@ $< This pattern is usually used on UNIX. However, on OS/2, gcc creates foo.exe not foo when an extension is not present, and Make check foo only. Therefore Make tries to build foo whenever called. * src/remake.c (f_mtime) [EMX]: Check a target again by

[bug #63650] Performance regression with EXPORT_ALL_VARIABLES enabled

2023-01-13 Thread Eli Zaretskii
Follow-up Comment #2, bug #63650 (project make): ??? Do you mean to say that commit f51fc130 caused this regression? If so, I don't understand: that commit changed code that is only used on MS-Windows, whereas the OP is on Arch Linux...

[bug #63650] Performance regression with EXPORT_ALL_VARIABLES enabled

2023-01-13 Thread Paul D. Smith
Follow-up Comment #3, bug #63650 (project make): I think they just mean they also tested Git HEAD (which is the commit mentioned) and see the same behavior as with the GNU Make 4.4 release. ___ Reply to this item at:

[bug #63650] Performance regression with EXPORT_ALL_VARIABLES enabled

2023-01-13 Thread Paul D. Smith
Follow-up Comment #4, bug #63650 (project make): I don't think this is a bug. Or, at least I don't think we can fix it. In previous versions of GNU Make we did not add make variables to the environment of the shell function regardless of their export status. So for example this makefile:

[bug #63650] Performance regression with EXPORT_ALL_VARIABLES enabled

2023-01-13 Thread anonymous
Follow-up Comment #1, bug #63650 (project make): Update: reproduces when building from git. Commit sha f51fc130, message: [SV 63638] Fix processing PATH on MS-Windows ___ Reply to this item at:

[bug #63650] Performance regression with EXPORT_ALL_VARIABLES enabled

2023-01-13 Thread anonymous
URL: Summary: Performance regression with EXPORT_ALL_VARIABLES enabled Project: make Submitter: None Submitted: Fri 13 Jan 2023 12:33:13 PM UTC Severity: 3 - Normal

Re: [PATCH] Check .exe as well when a target does not exist on OS/2

2023-01-13 Thread Eli Zaretskii
> From: KO Myung-Hun > Date: Fri, 13 Jan 2023 22:27:43 +0900 > > For example, > > foo: foo.c > gcc $@ $< > > This pattern is usually used on UNIX. However, on OS/2, gcc creates > foo.exe not foo when an extension is not present, and Make check foo > only. Therefore Make tries to build foo

Re: [PATCH] Check .exe as well when a target does not exist on OS/2

2023-01-13 Thread Paul Smith
On Fri, 2023-01-13 at 22:27 +0900, KO Myung-Hun wrote: > This pattern is usually used on UNIX. However, on OS/2, gcc creates > foo.exe not foo when an extension is not present, and Make check foo > only. Therefore Make tries to build foo whenever called. I don't think I like this change. I

[bug #63650] Performance regression with EXPORT_ALL_VARIABLES enabled

2023-01-13 Thread Paul D. Smith
Update of bug #63650 (project make): Item Group: Bug => Enhancement ___ Follow-up Comment #5: What about this idea: we would create a new environment when needed with all variables expanded,

[bug #63650] Performance regression with EXPORT_ALL_VARIABLES enabled

2023-01-13 Thread Paul D. Smith
Follow-up Comment #6, bug #63650 (project make): I guess we might be saved by a weird behavior of GNU Make that I've long considered changing because it confuses people: when we are about to expand a recipe we expand all lines in the recipe at once, before we invoke the first line. This means