Displaying 7 results from an estimated 7 matches for "creategvextractionpass".
2008 May 07
4
[LLVMdev] Missing passes
...can't seem to
find any code for. Where these removed?
Lower GC intrinsics, for GCless code generators (-lowergc)
Correlated Expression Elimination (-cee)
Lower select instructions to branches (-lowerselect)
Additionally, I found the following passes for which no documentation was
present:
createGVExtractionPass()
createStructRetPromotionPass()
createStripDeadPrototypesPass()
createJumpThreadingPass()
createMemCpyOptPass()
createLoopDeletionPass()
createCodeGenPreparePass()
From what I saw in Passes.html, the passes documentation is not generated
automatically? What's the policy on updating this...
2008 May 07
0
[LLVMdev] Missing passes
...sics, for GCless code generators (-lowergc)
Yes; this pass at least has been removed.
> Correlated Expression Elimination (-cee)
> Lower select instructions to branches (-lowerselect)
>
> Additionally, I found the following passes for which no
> documentation was present:
> createGVExtractionPass()
> createStructRetPromotionPass()
> createStripDeadPrototypesPass()
> createJumpThreadingPass()
> createMemCpyOptPass()
> createLoopDeletionPass()
> createCodeGenPreparePass()
>
> From what I saw in Passes.html, the passes documentation is not
> generated automat...
2012 Apr 21
0
[LLVMdev] Remove function from module
Михаил wrote:
> How correctly remove function from module?
> For example:
>
> int f1(int x) {
> ...
> a = f2(smth);
> ...
> }
> int f2 (int y) {
> ...
> b = f1(smth);
> ...
> }
>
> I need delete from module both f1 and f2. They haven't uses in other
> part of module, but I can't delete them with eraseFromParent, because
> they are use each
2012 Apr 21
3
[LLVMdev] Remove function from module
How correctly remove function from module?
For example:
int f1(int x) {
...
a = f2(smth);
...
}
int f2 (int y) {
...
b = f1(smth);
...
}
I need delete from module both f1 and f2. They haven't uses in other part of module, but I can't delete them with eraseFromParent, because they are use each other.
Yours sincerely,
Kadysev Mikhail
-------------- next part
2015 Jun 04
5
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
On Thu, Jun 4, 2015 at 3:58 PM, Duncan P. N. Exon Smith <
dexonsmith at apple.com> wrote:
>
> > Personally, I think the right approach is to add a bool to
> createGlobalDCEPass defaulting to true named something like
> IsAfterInlining. In most standard pass pipelines, GlobalDCE runs after
> inlining for obvious reasons, so the default makes sense. The special case
> is
2015 Jun 05
2
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
On Thu, Jun 4, 2015 at 5:33 PM, Reid Kleckner <rnk at google.com> wrote:
> On Thu, Jun 4, 2015 at 5:17 PM, Teresa Johnson <tejohnson at google.com> wrote:
>>
>> Agreed. Although I assume you mean invoke the new pass under a
>> ThinLTO-only option so that avail extern are not dropped in the
>> compile pass before the LTO link?
>
>
> No, this pass
2015 Jun 08
2
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
...---------------------===//
+/// createElimAvailExternPass - This transform is designed to eliminate
+/// available external globals (functions or global variables)
+///
+ModulePass *createElimAvailExternPass();
+
+//===----------------------------------------------------------------------===//
/// createGVExtractionPass - If deleteFn is true, this pass deletes
/// the specified global values. Otherwise, it deletes as much of the module as
/// possible, except for the global values specified.
Index: include/llvm/Transforms/IPO/PassManagerBuilder.h
==================================================================...