https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106932
TC changed:
What|Removed |Added
CC||rs2740 at gmail dot com
--- Comment #8 from TC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106932
--- Comment #7 from Jonathan Wakely ---
How would that work? The compile has no idea whether "source" is a regular file
or directory. Should it just suggest adding 'recursive' to the options whenever
a non-empty set of options is used?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106932
--- Comment #6 from Tom Allen ---
(In reply to Jonathan Wakely from comment #5)
> (In reply to Tom Allen from comment #4)
> > If this is the case, then when I have subdirectories which I explicitly do
> > not want to copy, but files at the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106932
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106932
--- Comment #4 from Tom Allen ---
(In reply to Jonathan Wakely from comment #2)
> I think this is the correct behaviour according to the standard.
>
> Where f is status("source") and t is status("dest").
>
> Effects are then as follows:
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106932
--- Comment #3 from Jonathan Wakely ---
(In reply to Tom Allen from comment #0)
> This appears to be contrary to bullet 4.7.4 in Section 29.11.14.3 of the
> C++20 spec, where for regular files in a source directory, the effect should
> be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106932
--- Comment #2 from Jonathan Wakely ---
I think this is the correct behaviour according to the standard.
Where f is status("source") and t is status("dest").
Effects are then as follows:
- If f.type() or t.type() is an implementation-defined
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106932
--- Comment #1 from Tom Allen ---
Created attachment 53573
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53573=edit
Preprocessor output for minimal testcase reproducing this issue.
