summary refs log tree commit diff
path: root/src/test/debuginfo
diff options
context:
space:
mode:
authorAlex Crichton <alex@alexcrichton.com>2015-04-10 13:39:51 -0700
committerAlex Crichton <alex@alexcrichton.com>2015-04-14 10:14:19 -0700
commit33fb5bb004613a0da01c2be272480c06fb82d6dc (patch)
tree60b42c52c7f0aa36fc3d06d028b3c98cd461aab2 /src/test/debuginfo
parent8f7eb3b058f78bffe5406776eb31080615799ce7 (diff)
downloadrust-33fb5bb004613a0da01c2be272480c06fb82d6dc.tar.gz
rust-33fb5bb004613a0da01c2be272480c06fb82d6dc.zip
bench: Fix fallout in benchmarks
Diffstat (limited to 'src/test/debuginfo')
-rw-r--r--src/test/debuginfo/function-arg-initialization.rs22
-rw-r--r--src/test/debuginfo/function-prologue-stepping-no-stack-check.rs26
-rw-r--r--src/test/debuginfo/issue13213.rs2
3 files changed, 25 insertions, 25 deletions
diff --git a/src/test/debuginfo/function-arg-initialization.rs b/src/test/debuginfo/function-arg-initialization.rs
index d611e4a65a6..a1ca59caa33 100644
--- a/src/test/debuginfo/function-arg-initialization.rs
+++ b/src/test/debuginfo/function-arg-initialization.rs
@@ -10,15 +10,15 @@
 
 // min-lldb-version: 310
 
-// This test case checks if function arguments already have the correct value when breaking at the
-// first line of the function, that is if the function prologue has already been executed at the
-// first line. Note that because of the __morestack part of the prologue GDB incorrectly breaks at
-// before the arguments have been properly loaded when setting the breakpoint via the function name.
+// This test case checks if function arguments already have the correct value
+// when breaking at the first line of the function, that is if the function
+// prologue has already been executed at the first line. Note that because of
+// the __morestack part of the prologue GDB incorrectly breaks at before the
+// arguments have been properly loaded when setting the breakpoint via the
+// function name.
 
 // compile-flags:-g
 
-#![feature(old_io)]
-
 // === GDB TESTS ===================================================================================
 
 // gdb-command:run
@@ -227,7 +227,7 @@
 #![omit_gdb_pretty_printer_section]
 
 fn immediate_args(a: isize, b: bool, c: f64) {
-    ::std::old_io::print("") // #break
+    println!("") // #break
 }
 
 struct BigStruct {
@@ -242,21 +242,21 @@ struct BigStruct {
 }
 
 fn non_immediate_args(a: BigStruct, b: BigStruct) {
-    ::std::old_io::print("") // #break
+    println!("") // #break
 }
 
 fn binding(a: i64, b: u64, c: f64) {
     let x = 0; // #break
-    ::std::old_io::print("")
+    println!("")
 }
 
 fn assignment(mut a: u64, b: u64, c: f64) {
     a = b; // #break
-    ::std::old_io::print("")
+    println!("")
 }
 
 fn function_call(x: u64, y: u64, z: f64) {
-    std::old_io::stdio::print("Hi!") // #break
+    println!("Hi!") // #break
 }
 
 fn identifier(x: u64, y: u64, z: f64) -> u64 {
diff --git a/src/test/debuginfo/function-prologue-stepping-no-stack-check.rs b/src/test/debuginfo/function-prologue-stepping-no-stack-check.rs
index 0608e49b28c..7e959a1e920 100644
--- a/src/test/debuginfo/function-prologue-stepping-no-stack-check.rs
+++ b/src/test/debuginfo/function-prologue-stepping-no-stack-check.rs
@@ -11,17 +11,17 @@
 // ignore-android: FIXME(#10381)
 // min-lldb-version: 310
 
-// This test case checks if function arguments already have the correct value when breaking at the
-// beginning of a function. Functions with the #[no_stack_check] attribute have the same prologue as
-// regular C functions compiled with GCC or Clang and therefore are better handled by GDB. As a
-// consequence, and as opposed to regular Rust functions, we can set the breakpoints via the
-// function name (and don't have to fall back on using line numbers). For LLDB this shouldn't make
-// a difference because it can handle both cases.
+// This test case checks if function arguments already have the correct value
+// when breaking at the beginning of a function. Functions with the
+// #[no_stack_check] attribute have the same prologue as regular C functions
+// compiled with GCC or Clang and therefore are better handled by GDB. As a
+// consequence, and as opposed to regular Rust functions, we can set the
+// breakpoints via the function name (and don't have to fall back on using line
+// numbers). For LLDB this shouldn't make a difference because it can handle
+// both cases.
 
 // compile-flags:-g
 
-#![feature(old_io)]
-
 // === GDB TESTS ===================================================================================
 
 // gdb-command:rbreak immediate_args
@@ -251,7 +251,7 @@
 
 #[no_stack_check]
 fn immediate_args(a: isize, b: bool, c: f64) {
-    ::std::old_io::print("");
+    println!("");
 }
 
 struct BigStruct {
@@ -267,24 +267,24 @@ struct BigStruct {
 
 #[no_stack_check]
 fn non_immediate_args(a: BigStruct, b: BigStruct) {
-    ::std::old_io::print("");
+    println!("");
 }
 
 #[no_stack_check]
 fn binding(a: i64, b: u64, c: f64) {
     let x = 0;
-    ::std::old_io::print("");
+    println!("");
 }
 
 #[no_stack_check]
 fn assignment(mut a: u64, b: u64, c: f64) {
     a = b;
-    ::std::old_io::print("");
+    println!("");
 }
 
 #[no_stack_check]
 fn function_call(x: u64, y: u64, z: f64) {
-    std::old_io::stdio::print("Hi!")
+    println!("Hi!")
 }
 
 #[no_stack_check]
diff --git a/src/test/debuginfo/issue13213.rs b/src/test/debuginfo/issue13213.rs
index 38b149ef243..13dc0c6d120 100644
--- a/src/test/debuginfo/issue13213.rs
+++ b/src/test/debuginfo/issue13213.rs
@@ -23,5 +23,5 @@ extern crate issue13213aux;
 // be available because they have been optimized out from the exporting crate.
 fn main() {
     let b: issue13213aux::S = issue13213aux::A;
-    ::std::old_io::println("Nothing to do here...");
+    println!("Nothing to do here...");
 }