2010-10-14 02:30:00 +02:00
|
|
|
; RUN: opt < %s -constprop -S | FileCheck %s
|
2009-10-05 07:26:04 +02:00
|
|
|
|
|
|
|
|
|
2011-03-27 16:26:13 +02:00
|
|
|
declare {i8, i1} @llvm.uadd.with.overflow.i8(i8, i8)
|
|
|
|
|
declare {i8, i1} @llvm.usub.with.overflow.i8(i8, i8)
|
|
|
|
|
declare {i8, i1} @llvm.umul.with.overflow.i8(i8, i8)
|
|
|
|
|
|
|
|
|
|
declare {i8, i1} @llvm.sadd.with.overflow.i8(i8, i8)
|
|
|
|
|
declare {i8, i1} @llvm.ssub.with.overflow.i8(i8, i8)
|
|
|
|
|
declare {i8, i1} @llvm.smul.with.overflow.i8(i8, i8)
|
|
|
|
|
|
2009-10-05 07:26:04 +02:00
|
|
|
;;-----------------------------
|
|
|
|
|
;; uadd
|
|
|
|
|
;;-----------------------------
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @uadd_1() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.uadd.with.overflow.i8(i8 42, i8 100)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @uadd_1(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -114, i1 false }
|
2009-10-05 07:26:04 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @uadd_2() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.uadd.with.overflow.i8(i8 142, i8 120)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @uadd_2(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 6, i1 true }
|
2009-10-05 07:26:04 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
;;-----------------------------
|
|
|
|
|
;; usub
|
|
|
|
|
;;-----------------------------
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @usub_1() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.usub.with.overflow.i8(i8 4, i8 2)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @usub_1(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 2, i1 false }
|
2009-10-05 07:26:04 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @usub_2() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.usub.with.overflow.i8(i8 4, i8 6)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @usub_2(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -2, i1 true }
|
2009-10-05 07:26:04 +02:00
|
|
|
}
|
|
|
|
|
|
2011-03-27 16:26:13 +02:00
|
|
|
;;-----------------------------
|
|
|
|
|
;; umul
|
|
|
|
|
;;-----------------------------
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @umul_1() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.umul.with.overflow.i8(i8 100, i8 3)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @umul_1(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 44, i1 true }
|
2011-03-27 16:26:13 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @umul_2() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.umul.with.overflow.i8(i8 100, i8 2)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @umul_2(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -56, i1 false }
|
2011-03-27 16:26:13 +02:00
|
|
|
}
|
|
|
|
|
|
2009-10-06 00:53:52 +02:00
|
|
|
;;-----------------------------
|
|
|
|
|
;; sadd
|
|
|
|
|
;;-----------------------------
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @sadd_1() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.sadd.with.overflow.i8(i8 42, i8 2)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @sadd_1(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 44, i1 false }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @sadd_2() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.sadd.with.overflow.i8(i8 120, i8 10)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @sadd_2(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -126, i1 true }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @sadd_3() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.sadd.with.overflow.i8(i8 -120, i8 10)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @sadd_3(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -110, i1 false }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @sadd_4() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.sadd.with.overflow.i8(i8 -120, i8 -10)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @sadd_4(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 126, i1 true }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @sadd_5() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.sadd.with.overflow.i8(i8 2, i8 -10)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @sadd_5(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -8, i1 false }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
;;-----------------------------
|
|
|
|
|
;; ssub
|
|
|
|
|
;;-----------------------------
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @ssub_1() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.ssub.with.overflow.i8(i8 4, i8 2)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @ssub_1(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 2, i1 false }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @ssub_2() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.ssub.with.overflow.i8(i8 4, i8 6)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @ssub_2(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -2, i1 false }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @ssub_3() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.ssub.with.overflow.i8(i8 -10, i8 120)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @ssub_3(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 126, i1 true }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @ssub_3b() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.ssub.with.overflow.i8(i8 -10, i8 10)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @ssub_3b(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -20, i1 false }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @ssub_4() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.ssub.with.overflow.i8(i8 120, i8 -10)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @ssub_4(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -126, i1 true }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @ssub_4b() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.ssub.with.overflow.i8(i8 20, i8 -10)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @ssub_4b(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 30, i1 false }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define {i8, i1} @ssub_5() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.ssub.with.overflow.i8(i8 -20, i8 -10)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @ssub_5(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -10, i1 false }
|
2009-10-06 00:53:52 +02:00
|
|
|
}
|
|
|
|
|
|
2011-03-27 16:26:13 +02:00
|
|
|
;;-----------------------------
|
|
|
|
|
;; smul
|
|
|
|
|
;;-----------------------------
|
2010-10-14 02:05:07 +02:00
|
|
|
|
|
|
|
|
; rdar://8501501
|
|
|
|
|
define {i8, i1} @smul_1() nounwind {
|
|
|
|
|
entry:
|
|
|
|
|
%t = call {i8, i1} @llvm.smul.with.overflow.i8(i8 -20, i8 -10)
|
|
|
|
|
ret {i8, i1} %t
|
|
|
|
|
|
2013-07-14 03:42:54 +02:00
|
|
|
; CHECK-LABEL: @smul_1(
|
Land the long talked about "type system rewrite" patch. This
patch brings numerous advantages to LLVM. One way to look at it
is through diffstat:
109 files changed, 3005 insertions(+), 5906 deletions(-)
Removing almost 3K lines of code is a good thing. Other advantages
include:
1. Value::getType() is a simple load that can be CSE'd, not a mutating
union-find operation.
2. Types a uniqued and never move once created, defining away PATypeHolder.
3. Structs can be "named" now, and their name is part of the identity that
uniques them. This means that the compiler doesn't merge them structurally
which makes the IR much less confusing.
4. Now that there is no way to get a cycle in a type graph without a named
struct type, "upreferences" go away.
5. Type refinement is completely gone, which should make LTO much MUCH faster
in some common cases with C++ code.
6. Types are now generally immutable, so we can use "Type *" instead
"const Type *" everywhere.
Downsides of this patch are that it removes some functions from the C API,
so people using those will have to upgrade to (not yet added) new API.
"LLVM 3.0" is the right time to do this.
There are still some cleanups pending after this, this patch is large enough
as-is.
llvm-svn: 134829
2011-07-09 19:41:24 +02:00
|
|
|
; CHECK: ret { i8, i1 } { i8 -56, i1 true }
|
2010-10-14 02:05:07 +02:00
|
|
|
}
|
