https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119152
Tomasz Kamiński changed:
What|Removed |Added
CC||tkaminsk at gcc dot gnu.org
R
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110339
Bug 110339 depends on bug 119152, which changed state.
Bug 119152 Summary: [C++26] P3019R14 indirect and polymorphic: Vocabulary Types
for Composite Class Design
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119152
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120481
--- Comment #8 from Tomasz Kamiński ---
%D is also affected by %m and %d.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120481
--- Comment #7 from Tomasz Kamiński ---
I am going for '%H' meaning the value of hours unmodified. The '%I' and '%p'
will work in terms of 24hours.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120481
--- Comment #5 from Tomasz Kamiński ---
> I think it's fine for the output to be unspecified in that case, since it's
> not a meaningful time-of-day.
I do not think that 50h from midnight is unspecified time of day, is 2 am in
next two days. T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120481
--- Comment #3 from Tomasz Kamiński ---
Similar problems exists when '%H' is used for duration with hours greater than
100:
```
std::chrono::seconds t = 255h + 24min + 2s;
std::cout << std::format("{:%H}", t) << std::endl; // prints 99
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120481
--- Comment #2 from Tomasz Kamiński ---
For weekday, we could also consider printing !ok() values unmodified. They
always will be greater than 7, so there is no confusion in the output.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120481
Tomasz Kamiński changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120481
--- Comment #1 from Tomasz Kamiński ---
Similar issue appears also for using '%w' and '%u' on the weekday that contains
a 2 or 3 digit number:
```
std::cout << std::format("{:%w}", weekday(120)) << std::endl; // prints 8
std::cout << std::format
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120481
Bug ID: 120481
Summary: Incorrect format result for using specifier with
multi-digit month, day or weekday
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119126
Tomasz Kamiński changed:
What|Removed |Added
CC||tkaminsk at gcc dot gnu.org
R
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110339
Bug 110339 depends on bug 119126, which changed state.
Bug 119126 Summary: [C++26] Implement P0792R14 function_ref: a type-erased
callable reference
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119126
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120259
--- Comment #4 from Tomasz Kamiński ---
> I agree we should revert the static_assert for the swappable traits.
I am most concerned with is_invocable family here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120259
--- Comment #2 from Tomasz Kamiński ---
This seems to be regeressions from PR1579:
r11-2759-g69f571ffc513b689fa26e4c9fceba17c2c989ab3
r11-3442-gc1fc9f6e10e646f01194c8f150affbc1cfbc404a
I think we went to eager there, and most likely should reve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120259
--- Comment #1 from Tomasz Kamiński ---
We should use _Arg&& in is_invokable checks here:
```
template
constexpr enable_if_t, _Res>
__invoke_r(_Callable&& __fn, _Args&&... __args)
noexcept(is_nothrow_invocable_r_v<_Res, _Callable,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110339
Bug 110339 depends on bug 119125, which changed state.
Bug 119125 Summary: [C++26] Implement P2548R6 copyable_function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119125
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119125
Tomasz Kamiński changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88322
Bug 88322 depends on bug 119246, which changed state.
Bug 119246 Summary: Result basic_format_arg::check_dynamic_spec is incorrect
for extended floating point types
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119246
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119246
Tomasz Kamiński changed:
What|Removed |Added
Target Milestone|--- |16.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120259
Bug ID: 120259
Summary: Using Incomplete&& as argument in
invoke_r/move_only_function fails to compile
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120259
Tomasz Kamiński changed:
What|Removed |Added
Known to fail||12.1.0
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120114
Tomasz Kamiński changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120114
Tomasz Kamiński changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120114
Bug ID: 120114
Summary: Format width is not correctly handled for chrono
formatting
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119970
--- Comment #6 from Tomasz Kamiński ---
Yes, this allows us to avoid a separate allocation when transcoding to valid
Unicode. For reference in libstdc++-v3/src/c++23/print.cc, to_valid_unicode
will edit sequence in-situ:
```
// If sizeof(_Char
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119970
--- Comment #4 from Tomasz Kamiński ---
I would be grateful, if you could confirm that above fixed the build for you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119970
--- Comment #2 from Tomasz Kamiński ---
The fails only occurs on WIN32, i.e. if defined(_WIN32) &&
!defined(__CYGWIN__).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119970
Tomasz Kamiński changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |tkaminsk at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109162
--- Comment #26 from Tomasz Kamiński ---
The latest commit (optimization) is for GCC 16 only.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109162
--- Comment #24 from Tomasz Kamiński ---
> Although it doesn't seem to be in the upcoming GCC-15 release.
GCC 15.1 has everything expect formatters for adaptors. So ranges, debug
presentation, pair, tuple and std::vector::reference will be in.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109162
--- Comment #22 from Tomasz Kamiński ---
> That is highly intentional to fix incorrect formatting when the container is
> a string. See https://cplusplus.github.io/LWG/issue3881
I am well aware of this quirk, but my implementation uses range_f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109162
Tomasz Kamiński changed:
What|Removed |Added
CC||tkaminsk at gcc dot gnu.org
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119918
Tomasz Kamiński changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119918
--- Comment #1 from Tomasz Kamiński ---
This is similar to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119517.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119918
Tomasz Kamiński changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119918
Bug ID: 119918
Summary: formattable returns true for types
other than char and wchar_t
Product: gcc
Version: 14.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119840
--- Comment #4 from Tomasz Kamiński ---
I would like to get confirmation from John David Anglin, that warnings no
longer appear on the target.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119840
Tomasz Kamiński changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119754
--- Comment #3 from Tomasz Kamiński ---
Except that `::operator new` does not perform implicit object creation at
compile time per https://eel.is/c++draft/intro.object#14:
> Except during constant evaluation, any implicit or explicit invocation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119754
Tomasz Kamiński changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119725
Tomasz Kamiński changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |tkaminsk at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119725
--- Comment #2 from Tomasz Kamiński ---
I do not (yet) have access to solaris machine. Would it be possible for you to
verify that all tests passes with following adjustments:
diff --git a/libstdc++-v3/testsuite/std/format/debug.cc
b/libstdc++-v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119725
Tomasz Kamiński changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111055
Tomasz Kamiński changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106749
Bug 106749 depends on bug 111055, which changed state.
Bug 111055 Summary: [C++23] Implement P1206R7, Conversions from ranges to
containers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111055
What|Removed |Add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119415
Bug 119415 depends on bug 111055, which changed state.
Bug 111055 Summary: [C++23] Implement P1206R7, Conversions from ranges to
containers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111055
What|Removed |Add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111053
Bug 111053 depends on bug 111055, which changed state.
Bug 111055 Summary: [C++23] Implement P1206R7, Conversions from ranges to
containers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111055
What|Removed |Add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111055
Tomasz Kamiński changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116958
Bug 116958 depends on bug 111055, which changed state.
Bug 111055 Summary: [C++23] Implement P1206R7, Conversions from ranges to
containers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111055
What|Removed |Add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119593
Tomasz Kamiński changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119593
--- Comment #3 from Tomasz Kamiński ---
Two separate problems compound in this case:
* UTF-32LE, UTF-32BE used for wchar_t, are not recognized as unicode encoding
* character with is always assumed to be 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119593
--- Comment #2 from Tomasz Kamiński ---
The problem is not limited to wide characters, and also appears for wide
strings:
std::format(L"{:+<3}", L"\U0001f921"); // two '+' of paddings
// https://godbolt.org/z/o4s7qTEz9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119593
Tomasz Kamiński changed:
What|Removed |Added
Summary|Format width is not |Format width is not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119593
Bug ID: 119593
Summary: Format width is not correctly handled for unicode
characters
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119517
Tomasz Kamiński changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119517
--- Comment #2 from Tomasz Kamiński ---
Jonathan noted that zoned_time is specified in standard to accept unconstrained
FormatContext in [time.format] p19 (https://eel.is/c++draft/time.format#19).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119517
Tomasz Kamiński changed:
What|Removed |Added
Version|13.0|15.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119517
Bug ID: 119517
Summary: formatter for chrono types are underconstrained
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119415
--- Comment #19 from Tomasz Kamiński ---
Updated resolution to use __has_input_iter_cat instead of
__cpp17_input_iterator.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119415
--- Comment #17 from Tomasz Kamiński ---
In the same file we have: __has_input_iter_cat.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119415
--- Comment #12 from Tomasz Kamiński ---
I have realized that with the resolution of the
https://cplusplus.github.io/LWG/lwg-defects.html#3749, you can run into this
problem by doing:
auto r = std::views::iota(__int128(0)) | std::views::take(5)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119415
--- Comment #9 from Tomasz Kamiński ---
> Hum, meeting Cpp17LegacyIterator requirements does not mean it is a C++17
> input iterator, only iterator_traits::iterator_category represents its
> category, so __cpp17_input_iterator should not be us
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119415
Tomasz Kamiński changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |tkaminsk at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119415
--- Comment #4 from Tomasz Kamiński ---
If want to support user-defined containers, I think we should check if
iterator_traits::iterator category exists, before calling insert(Iterator,
Iterator) overload.
This will prevent hard-errors from old
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111055
--- Comment #16 from Tomasz Kamiński ---
The changes are also required for .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119358
Tomasz Kamiński changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119358
Tomasz Kamiński changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111055
--- Comment #15 from Tomasz Kamiński ---
The still remains to be implemented.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38
Tomasz Kamiński changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108053
Tomasz Kamiński changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108053
Tomasz Kamiński changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88322
Bug 88322 depends on bug 108053, which changed state.
Bug 108053 Summary: std::visit_format_arg should hide __int128 and other
extensions behind a handle
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108053
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119246
Tomasz Kamiński changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119246
--- Comment #2 from Tomasz Kamiński ---
We should also see if we can format `_Float128` and `__float128` by casting to
either of them. Similary how we handle `_Float32` and other type now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119246
--- Comment #1 from Tomasz Kamiński ---
As described in PR108053, this problem is caused by normalization of this
floating point types to standard floating point type, where they have same
representation. We lost the information about the source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108053
Tomasz Kamiński changed:
What|Removed |Added
CC||tkaminsk at gcc dot gnu.org
Last re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119246
Bug ID: 119246
Summary: Result basic_format_arg::check_dynamic_spec is
incorrect for extended floating point types
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38
Tomasz Kamiński changed:
What|Removed |Added
Severity|normal |minor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38
--- Comment #2 from Tomasz Kamiński ---
The issue is caused by the fact that we do not check `move_constructible &&
regular_invocable` (required by [range.zip.transform] p2.1.1) for
`sizeof...(_Ts) == 0` case.
```
struct _ZipTransform
{
templa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38
Tomasz Kamiński changed:
What|Removed |Added
Last reconfirmed||2025-03-07
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119121
--- Comment #2 from Tomasz Kamiński ---
Committed to master as r15-7830-g95b2f8d8fb3131
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119121
Tomasz Kamiński changed:
What|Removed |Added
Last reconfirmed||2025-03-05
Status|UNCONFI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119121
--- Comment #1 from Tomasz Kamiński ---
Introduced in g:65b4cba9d6a9ffe9b4d4bdff90727a7064cc0e3b
The `is_reference_v<_Vp>` should use `_Tp` instead.
```
template
concept __pair_like_convertible_from
- = !range<_Tp> && __pair_l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119121
Tomasz Kamiński changed:
What|Removed |Added
Known to work||13.3.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119121
Bug ID: 119121
Summary: subrange conversion to tuple-like does not work
Product: gcc
Version: 14.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
85 matches
Mail list logo
