Skip to content

[WIP]Unique stable name #310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 27 commits into from
Closed

Conversation

schittir
Copy link
Contributor

@schittir schittir commented May 4, 2021

Add tests to Erich's patch

Erich Keane and others added 27 commits April 23, 2021 08:22
'Expr' type, which required a ton of implementation... Whew, at least
that is over.  A couple of 'TODO's remain, but we'll get to those
eventually.
… the name/mark the name, and some other various TODOs there
…e in both SEMA and CodeGen without duplication
…mbda' registration is a little wrong right now though
I was trying to use the same lambda to do 2 different things, determine
whether the lambda needed this mangling, and doing the mangling.
Unfortuantely the logic/split there was not particularly useful.

Changed back to have these function-pointers always be populated and
switched to 2 different calls.  This allows us to not have a conflict on
not-participate-in-kernel with lambda ID #0 and ID#1 (0 is supposed to
be mangled as an unnamed struct, and #1 is mangled with id 0).
This just makes it not particularly usable in the clang-c interface,
which I believe we're OK with.  In the future, we can re-add this
behavior if we care to.
The load was doing some funny stuff trying to turn the type of our
builtin into an i8 instead of an i8*.  However, it seems that when we
use a global we typically just want to wrap it in a GEP to get the 1st
element.  This is auto-generated for us if we jsut return the string
itself.
…rrect AS, then addr-space-cast if necessary
@repo-lockdown
Copy link

repo-lockdown bot commented May 4, 2021

This repository does not accept pull requests. Please follow http://llvm.org/docs/Contributing.html#how-to-submit-a-patch for contribution to LLVM.

@repo-lockdown repo-lockdown bot closed this May 4, 2021
@repo-lockdown repo-lockdown bot locked and limited conversation to collaborators May 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant