Răsfoiți Sursa

* synchronised with trunk till r42053

git-svn-id: branches/debug_eh@42054 -
Jonas Maebe 6 ani în urmă
părinte
comite
6d597e1286
2 a modificat fișierele cu 0 adăugiri și 20 ștergeri
  1. 0 13
      tests/test/cg/tcalpext.pp
  2. 0 7
      tests/test/talign2.pp

+ 0 - 13
tests/test/cg/tcalpext.pp

@@ -27,18 +27,5 @@ uses
   ctypes
   ;
 
-
-{$ifdef USE_PASCAL_OBJECT}
-  {$ifdef win32}
-    {$ifdef ver1_0}
-      {$L ptest.ow}
-    {$else}
-      {$L ptest.o}
-    {$endif}
-  {$else}
-  {$L ptest.o}
-  {$endif not win32}
-{$endif USE_PASCAL_OBJECT}
-
 {$i tcalext.pp }
 

+ 0 - 7
tests/test/talign2.pp

@@ -3,9 +3,6 @@
 { This verifies if the strings are
   correctly aligned, normally the generated assembler
   should be verified manually.
-
-  I consider this test as flawed, or is there a reason, why a
-  shortstring should be aligned to pointer boundaries? (FK)
 }
 program talign2;
 
@@ -78,16 +75,12 @@ const
 {$ifdef haswidestring}
   widestr : widestring = 'simple widestring';
 {$endif}
-  shortstr :shortstring = 'simple shortstring';
 begin
   test(length(ansistr)=17);
 {$ifdef haswidestring}
   test(length(widestr)=17);
 {$endif}
-  test(length(shortstr)=18);
   { verify if the address are correctly aligned! }
-  pt:=@shortstr;
-  test((ptruint(pt) mod pointer_alignment)=0);
   pt:=p;
   test((ptruint(pt) mod pointer_alignment)=0);
   pt:=pchar(ansistr);