maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/polly/test/ScopDetectionDiagnostics/ReportAlias-01.ll

70 lines
3.6 KiB
LLVM
Raw Normal View History

ScopDetection: Only detect scops that have at least one read and one write Scops that only read seem generally uninteresting and scops that only write are most likely initializations where there is also little to optimize. To not waste compile time we bail early. Differential Revision: http://reviews.llvm.org/D7735 llvm-svn: 229820
2015-02-19 13:31:07 +08:00
; RUN: opt %loadPolly -polly-detect-unprofitable -polly-use-runtime-alias-checks=false -pass-remarks-missed="polly-detect" -polly-detect-track-failures -polly-detect -analyze < %s 2>&1| FileCheck %s
Diagnostic: Provide end-user message for aliasing errors This will spill out information about LLVM-internals. However, in cases where the name of the Value matches the name of the array in the source, we provide more useful information. In cases where we spill internals, the information still might help the user to pin down the correct arrays. The problem we face here is: The error is pinned to the debug location of one of the offending values out of the alias set instead of all of them. The more information we give the user about the set of aliasing pointers the better. llvm-svn: 215830
2014-08-17 18:09:07 +08:00
;void f(int A[], int B[]) {
; for (int i=0; i<42; i++)
; A[i] = B[i];
;}
; CHECK: remark: ReportAlias-01.c:2:8: The following errors keep this region from being a Scop.
Report possible aliasing deterministically This commit drops a call to std::sort, which sorted the base pointers that possibly alias according to the address at which their corresponding llvm::Value was allocated. There does not seem to be any good reason, why those pointers should be (re)sorted and this only makes the output indeterministic. llvm-svn: 218052
2014-09-18 22:45:43 +08:00
; CHECK: remark: ReportAlias-01.c:3:5: Accesses to the arrays "B", "A" may access the same memory.
Diagnostic: Provide end-user message for aliasing errors This will spill out information about LLVM-internals. However, in cases where the name of the Value matches the name of the array in the source, we provide more useful information. In cases where we spill internals, the information still might help the user to pin down the correct arrays. The problem we face here is: The error is pinned to the debug location of one of the offending values out of the alias set instead of all of them. The more information we give the user about the set of aliasing pointers the better. llvm-svn: 215830
2014-08-17 18:09:07 +08:00
; CHECK: remark: ReportAlias-01.c:3:5: Invalid Scop candidate ends here.
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
define void @f(i32* %A, i32* %B) {
entry:
br label %entry.split
entry.split: ; preds = %entry
Update polly for LLVM rename of debug info metadata with DI* prefix Ran the same rename-md-di-prefix.sh script attached to PR23080 as in LLVM r236120 and CFE r236121. llvm-svn: 236127
2015-04-30 01:02:14 +08:00
tail call void @llvm.dbg.value(metadata i32* %A, i64 0, metadata !13, metadata !DIExpression()), !dbg !14
tail call void @llvm.dbg.value(metadata i32* %B, i64 0, metadata !15, metadata !DIExpression()), !dbg !16
tail call void @llvm.dbg.value(metadata i32 0, i64 0, metadata !18, metadata !DIExpression()), !dbg !20
Diagnostic: Provide end-user message for aliasing errors This will spill out information about LLVM-internals. However, in cases where the name of the Value matches the name of the array in the source, we provide more useful information. In cases where we spill internals, the information still might help the user to pin down the correct arrays. The problem we face here is: The error is pinned to the debug location of one of the offending values out of the alias set instead of all of them. The more information we give the user about the set of aliasing pointers the better. llvm-svn: 215830
2014-08-17 18:09:07 +08:00
br label %for.body, !dbg !21
for.body: ; preds = %entry.split, %for.body
%indvar = phi i64 [ 0, %entry.split ], [ %indvar.next, %for.body ]
Update Polly tests to handle explicitly typed gep changes in LLVM llvm-svn: 230784
2015-02-28 03:20:19 +08:00
%arrayidx = getelementptr i32, i32* %B, i64 %indvar, !dbg !22
%arrayidx2 = getelementptr i32, i32* %A, i64 %indvar, !dbg !22
Update Polly tests to handle explicitly typed load changes in LLVM. llvm-svn: 230796
2015-02-28 05:22:50 +08:00
%0 = load i32, i32* %arrayidx, align 4, !dbg !22
Diagnostic: Provide end-user message for aliasing errors This will spill out information about LLVM-internals. However, in cases where the name of the Value matches the name of the array in the source, we provide more useful information. In cases where we spill internals, the information still might help the user to pin down the correct arrays. The problem we face here is: The error is pinned to the debug location of one of the offending values out of the alias set instead of all of them. The more information we give the user about the set of aliasing pointers the better. llvm-svn: 215830
2014-08-17 18:09:07 +08:00
store i32 %0, i32* %arrayidx2, align 4, !dbg !22
Update polly for LLVM rename of debug info metadata with DI* prefix Ran the same rename-md-di-prefix.sh script attached to PR23080 as in LLVM r236120 and CFE r236121. llvm-svn: 236127
2015-04-30 01:02:14 +08:00
tail call void @llvm.dbg.value(metadata !{null}, i64 0, metadata !18, metadata !DIExpression()), !dbg !20
Diagnostic: Provide end-user message for aliasing errors This will spill out information about LLVM-internals. However, in cases where the name of the Value matches the name of the array in the source, we provide more useful information. In cases where we spill internals, the information still might help the user to pin down the correct arrays. The problem we face here is: The error is pinned to the debug location of one of the offending values out of the alias set instead of all of them. The more information we give the user about the set of aliasing pointers the better. llvm-svn: 215830
2014-08-17 18:09:07 +08:00
%indvar.next = add i64 %indvar, 1, !dbg !21
%exitcond = icmp ne i64 %indvar.next, 42, !dbg !21
br i1 %exitcond, label %for.body, label %for.end, !dbg !21
for.end: ; preds = %for.body
ret void, !dbg !23
}
Upgrade testcases after LLVM r234181 Until r234181 we were silently upgrading old `@llvm.dbg` intrinsics. Fix testcases in polly that were relying on that. llvm-svn: 234192
2015-04-07 02:25:51 +08:00
declare void @llvm.dbg.declare(metadata, metadata, metadata)
declare void @llvm.dbg.value(metadata, i64, metadata, metadata)
Diagnostic: Provide end-user message for aliasing errors This will spill out information about LLVM-internals. However, in cases where the name of the Value matches the name of the array in the source, we provide more useful information. In cases where we spill internals, the information still might help the user to pin down the correct arrays. The problem we face here is: The error is pinned to the debug location of one of the offending values out of the alias set instead of all of them. The more information we give the user about the set of aliasing pointers the better. llvm-svn: 215830
2014-08-17 18:09:07 +08:00
!llvm.dbg.cu = !{!0}
!llvm.module.flags = !{!10, !11}
!llvm.ident = !{!12}
Update polly for LLVM rename of debug info metadata with DI* prefix Ran the same rename-md-di-prefix.sh script attached to PR23080 as in LLVM r236120 and CFE r236121. llvm-svn: 236127
2015-04-30 01:02:14 +08:00
!0 = !DICompileUnit(language: DW_LANG_C99, producer: "clang version 3.6.0 ", isOptimized: false, emissionKind: 1, file: !1, enums: !2, retainedTypes: !2, subprograms: !3, globals: !2, imports: !2)
!1 = !DIFile(filename: "ReportAlias-01.c", directory: "test/ScopDetectionDiagnostic/")
Run upgrade script from PR21532 to match LLVM changes Update tests for LLVM assembly format change in r224257 using the script attached to PR21532. I'm hoping this unsticks the bot [1]. [1]: http://lab.llvm.org:8011/builders/polly-amd64-linux/builds/25432 llvm-svn: 224269
2014-12-16 04:28:50 +08:00
!2 = !{}
!3 = !{!4}
Update polly for LLVM rename of debug info metadata with DI* prefix Ran the same rename-md-di-prefix.sh script attached to PR23080 as in LLVM r236120 and CFE r236121. llvm-svn: 236127
2015-04-30 01:02:14 +08:00
!4 = !DISubprogram(name: "f", line: 1, isLocal: false, isDefinition: true, virtualIndex: 6, flags: DIFlagPrototyped, isOptimized: false, scopeLine: 1, file: !1, scope: !5, type: !6, function: void (i32*, i32*)* @f, variables: !2)
!5 = !DIFile(filename: "ReportAlias-01.c", directory: "test/ScopDetectionDiagnostic/")
!6 = !DISubroutineType(types: !7)
Run upgrade script from PR21532 to match LLVM changes Update tests for LLVM assembly format change in r224257 using the script attached to PR21532. I'm hoping this unsticks the bot [1]. [1]: http://lab.llvm.org:8011/builders/polly-amd64-linux/builds/25432 llvm-svn: 224269
2014-12-16 04:28:50 +08:00
!7 = !{null, !8, !8}
Update polly for LLVM rename of debug info metadata with DI* prefix Ran the same rename-md-di-prefix.sh script attached to PR23080 as in LLVM r236120 and CFE r236121. llvm-svn: 236127
2015-04-30 01:02:14 +08:00
!8 = !DIDerivedType(tag: DW_TAG_pointer_type, size: 64, align: 64, baseType: !9)
!9 = !DIBasicType(tag: DW_TAG_base_type, name: "int", size: 32, align: 32, encoding: DW_ATE_signed)
Run upgrade script from PR21532 to match LLVM changes Update tests for LLVM assembly format change in r224257 using the script attached to PR21532. I'm hoping this unsticks the bot [1]. [1]: http://lab.llvm.org:8011/builders/polly-amd64-linux/builds/25432 llvm-svn: 224269
2014-12-16 04:28:50 +08:00
!10 = !{i32 2, !"Dwarf Version", i32 4}
Update Polly tests for the great metadata schema change llvm-svn: 231089
2015-03-04 02:17:26 +08:00
!11 = !{i32 2, !"Debug Info Version", i32 3}
Run upgrade script from PR21532 to match LLVM changes Update tests for LLVM assembly format change in r224257 using the script attached to PR21532. I'm hoping this unsticks the bot [1]. [1]: http://lab.llvm.org:8011/builders/polly-amd64-linux/builds/25432 llvm-svn: 224269
2014-12-16 04:28:50 +08:00
!12 = !{!"clang version 3.6.0 "}
Fix polly tests after LLVM IR change in r243774 llvm-svn: 243801
2015-08-01 07:58:50 +08:00
!13 = !DILocalVariable(name: "A", line: 1, arg: 1, scope: !4, file: !5, type: !8)
Update polly for LLVM rename of debug info metadata with DI* prefix Ran the same rename-md-di-prefix.sh script attached to PR23080 as in LLVM r236120 and CFE r236121. llvm-svn: 236127
2015-04-30 01:02:14 +08:00
!14 = !DILocation(line: 1, column: 12, scope: !4)
Fix polly tests after LLVM IR change in r243774 llvm-svn: 243801
2015-08-01 07:58:50 +08:00
!15 = !DILocalVariable(name: "B", line: 1, arg: 2, scope: !4, file: !5, type: !8)
Update polly for LLVM rename of debug info metadata with DI* prefix Ran the same rename-md-di-prefix.sh script attached to PR23080 as in LLVM r236120 and CFE r236121. llvm-svn: 236127
2015-04-30 01:02:14 +08:00
!16 = !DILocation(line: 1, column: 21, scope: !4)
Run upgrade script from PR21532 to match LLVM changes Update tests for LLVM assembly format change in r224257 using the script attached to PR21532. I'm hoping this unsticks the bot [1]. [1]: http://lab.llvm.org:8011/builders/polly-amd64-linux/builds/25432 llvm-svn: 224269
2014-12-16 04:28:50 +08:00
!17 = !{i32 0}
Fix polly tests after LLVM IR change in r243774 llvm-svn: 243801
2015-08-01 07:58:50 +08:00
!18 = !DILocalVariable(name: "i", line: 2, scope: !19, file: !5, type: !9)
Update polly for LLVM rename of debug info metadata with DI* prefix Ran the same rename-md-di-prefix.sh script attached to PR23080 as in LLVM r236120 and CFE r236121. llvm-svn: 236127
2015-04-30 01:02:14 +08:00
!19 = distinct !DILexicalBlock(line: 2, column: 3, file: !1, scope: !4)
!20 = !DILocation(line: 2, column: 12, scope: !19)
!21 = !DILocation(line: 2, column: 8, scope: !19)
!22 = !DILocation(line: 3, column: 5, scope: !19)
!23 = !DILocation(line: 4, column: 1, scope: !4)