It affects the build, and if used as a static file, can reliably be
tracked using the `-MF` mechanism.
gcc/cp/:
* mapper-client.cc, mapper-client.h (open_module_client): Accept
dependency tracking and track module mapper files as
dependencies.
* module.cc (make_map
This patch implements support for [P1689R5][] to communicate to a build
system the C++20 module dependencies to build systems so that they may
build `.gcm` files in the proper order.
Support is communicated through the following three new flags:
- `-fdeps-format=` specifies the format for the out
Unicode does not support such values because they are unrepresentable in
UTF-16.
libcpp/
* charset.cc: Reject encodings of codepoints above 0x10.
UTF-16 does not support such codepoints and therefore all
Unicode rejects such values.
Signed-off-by: Ben Boeckel
---
li
They affect the build, so report them via `-MF` mechanisms.
gcc/cp/
* module.cc (do_import): Report imported CMI files as
dependencies.
Signed-off-by: Ben Boeckel
---
gcc/cp/module.cc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
ind
Hi,
This patch series adds initial support for ISO C++'s [P1689R5][], a
format for describing C++ module requirements and provisions based on
the source code. This is required because compiling C++ with modules is
not embarrassingly parallel and need to be ordered to ensure that
`import some_modul
On Tue, 6 Jun 2023 at 20:14, Thomas Schwinge
wrote:
> Hi!
>
> This issue comes up in context of me working on C++ support for GCN and
> nvptx target. Those targets shall default to '-fno-exceptions' -- or,
> "in other words", '-fexceptions' is not supported. (Details omitted
> here.)
>
> It did
Hi!
This issue comes up in context of me working on C++ support for GCN and
nvptx target. Those targets shall default to '-fno-exceptions' -- or,
"in other words", '-fexceptions' is not supported. (Details omitted
here.)
It did seem clear to me that with such a configuration it'll be hard to
ge
David Edelsohn writes:
> The GNU Toolchain leadership has blacklisted people in the past, but we
> have used the power sparingly.
>
> The behavior of the individual attracts attention, albeit negative, while
> not effectively accomplishing what he purports to desire. The recommended
> solution
On Tue, Jun 6, 2023 at 11:38 AM David Brown via Gcc wrote:
> On 06/06/2023 14:53, Paul Smith wrote:
> > On Tue, 2023-06-06 at 16:36 +0800, Julian Waters via Gcc wrote:
> >> Sorry for my outburst, to the rest of this list. I can no longer stay
> >> silent and watch these little shits bully people
On Tue, Jun 6, 2023 at 1:08 PM Umesh Kalappa via Gcc
wrote:
> Hi Segher ,
>
> >>What did you expect, what happened instead?
> For example the complex args are passed in GPR's for cexp in the case
> GCC and Clang uses caller memory .
>
> for reference : https://godbolt.org/z/MfMz3cTe7
>
> We hav
On Tue, 6 Jun 2023, Andrew Pinski via Gcc wrote:
> You are looking at the wrong ABI document.
> That is for the 64bit ABI.
> The 32bit ABI document is located at:
> http://refspecs.linux-foundation.org/elf/elfspec_ppc.pdf
>
> Plus the 32bit ABI document does not document Complex argument passing
Hi Segher ,
>>What did you expect, what happened instead?
For example the complex args are passed in GPR's for cexp in the case
GCC and Clang uses caller memory .
for reference : https://godbolt.org/z/MfMz3cTe7
We have cross tools like some of libraries built using the GCC and
some use Clan
Hi!
On Tue, Jun 06, 2023 at 08:35:22PM +0530, Umesh Kalappa wrote:
> Hi Adnrew,
> Thank you for the quick response and for PPC64 too ,we do have
> mismatches in ABI b/w complex operations like
> https://godbolt.org/z/bjsYovx4c .
>
> Any reason why GCC chose to use GPR 's here ?
What did you expe
On 06/06/2023 14:53, Paul Smith wrote:
On Tue, 2023-06-06 at 16:36 +0800, Julian Waters via Gcc wrote:
Sorry for my outburst, to the rest of this list. I can no longer stay
silent and watch these little shits bully people who are too kind to
fire back with the same kind of venom in their words.
On Tue, Jun 6, 2023 at 8:05 AM Umesh Kalappa wrote:
>
> Hi Adnrew,
> Thank you for the quick response and for PPC64 too ,we do have
> mismatches in ABI b/w complex operations like
> https://godbolt.org/z/bjsYovx4c .
>
> Any reason why GCC chose to use GPR 's here ?
Yes because it was set before 2
Hi Adnrew,
Thank you for the quick response and for PPC64 too ,we do have
mismatches in ABI b/w complex operations like
https://godbolt.org/z/bjsYovx4c .
Any reason why GCC chose to use GPR 's here ?
~Umesh
On Tue, Jun 6, 2023 at 8:28 PM Andrew Pinski wrote:
>
> On Tue, Jun 6, 2023 at 7:50 AM U
On Tue, Jun 6, 2023 at 7:50 AM Umesh Kalappa via Libc-alpha
wrote:
>
> Hi all ,
>
> For the test case https://godbolt.org/z/vjs1vfs5W ,we see the mismatch
> in the ABI b/w gcc and clang .
>
> Do we have any supporting documents that second the GCC behaviour over CLANG ?
>
> EABI states like
>
> In
Hi all ,
For the test case https://godbolt.org/z/vjs1vfs5W ,we see the mismatch
in the ABI b/w gcc and clang .
Do we have any supporting documents that second the GCC behaviour over CLANG ?
EABI states like
In the Power Architecture 64-Bit ELF V2 ABI Specification document
(v1.1 from 16 July 20
On Tue, 2023-06-06 at 16:36 +0800, Julian Waters via Gcc wrote:
> Sorry for my outburst, to the rest of this list. I can no longer stay
> silent and watch these little shits bully people who are too kind to
> fire back with the same kind of venom in their words.
Many of us have had Dave in our kil
Hi David,
Sorry I didn't answer you earlier, I was busy concluding my term.
Finally finished yesterday, I now have 100% of my time for GCC.
I build yesterday the analyzer with -fanalyzer enabled. Globally there
are not many coherent warnings, and a common issue are the thesis-long
warnings.
Below
It's alright Gabriel, pay this intellectually challenged individual no
mind. It's clear that, unlike Stefan, who at the very least knows how to
disassemble native code and understands what the instruction sequences mean
(even though the way he goes about it is flat out wrong), this retard
doesn't k
On 06/06/2023 02:09, Dave Blanchard wrote:
If this guy's threads are such a terrible waste of your time, how
about employing your email client's filters to ignore his posts (and
mine too) and fuck off?
You apparently appreciate Stefan's posts, but burst a blood vessel when
reading anyone els
On Tue, 6 Jun 2023, 01:07 Dave Blanchard, wrote:
> On Tue, 6 Jun 2023 01:59:42 +0200
> Gabriel Ravier wrote:
>
> > [nothing of value]
>
> If this guy's threads are such a terrible waste of your time, how about
> employing your email client's filters to ignore his posts (and mine too)
> and fuck
23 matches
Mail list logo
