https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
David Edelsohn changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
--- Comment #11 from Bill Schmidt ---
After some experiments, we've found that a better approach is to continue using
the current poor-man's overloading scheme, and do more folding of built-in
calls following gimplification. David, should we clo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
--- Comment #10 from Yu Xuanchi ---
So there is currently i'm working on:
-Add "OVERLOAD" tree or just use chain. So we can put all function with same
identifier overloaded in a same tree so we can obtain them use
build_external_ref.
-Find a way
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
--- Comment #9 from Bill Schmidt ---
(In reply to Yu Xuanchi from comment #6)
> So I think in short term. We just reject those code. Because our aim is to
> support this feature like clang. If there is no any problem. I'll go impl it.
Agreed, we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
--- Comment #8 from Yu Xuanchi ---
I have test extern "C" in clang. Look like clang dose not actually mangled it
to "C format". I think because clang C front-end actually not have any mangle
logic. So it just mangled it like CPP front-end does.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
--- Comment #7 from Yu Xuanchi ---
And there is another option. Because clang documentation say:
"However, when an overloadable function occurs within an extern "C" linkage
specification, it’s name will be mangled in the same way as it would in C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
--- Comment #6 from Yu Xuanchi ---
So I think in short term. We just reject those code. Because our aim is to
support this feature like clang. If there is no any problem. I'll go impl it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
--- Comment #5 from Yu Xuanchi ---
So there is a problem clang does not support nested function. Like:
-
void foo() {
void foo1() {
// Bar
}
}
-
And cpp also not supported. But gcc support it as an extensions. So how we deal
with code lik
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
Yu Xuanchi changed:
What|Removed |Added
CC||yuxuanchiadm at 126 dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
--- Comment #3 from David Edelsohn ---
How does _Generic interact with C++ if one includes the same header file in
either language?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
David Edelsohn changed:
What|Removed |Added
CC||wschmidt at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
--- Comment #1 from Richard Biener ---
Doesn't C have generics for this now?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71199
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
13 matches
Mail list logo
