summaryrefslogtreecommitdiff
path: root/fpcsrc/tests/test/talign2.pp
blob: b6b08cf0ac8cd1bce82e79e2a6a1ed4048e0e525 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
{ %VERSION=1.1 }
{%OPT=-Og}
{ 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;

{$ifdef fpc}
{$mode objfpc}
{$define haswidestring}
{$else}
  {$ifndef ver70}
    {$define haswidestring}
  {$endif}
{$endif}

{$ifdef fpc}
{$ifdef unix}
uses
  cwstring;
{$endif}
{$endif}


procedure test(b : boolean);
begin
  if b then exit;
  WriteLn('Error in length/alignment!!');
  halt(1);
end;

var
 pt: pchar;
const
  b: byte = 0;  { lets just misalign the stuff }
  p : pchar = 'simple pchar stuff';
  ansistr : ansistring = 'simple ansistring';
{$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 sizeof(pointer))=0);
  pt:=p;
  test((ptruint(pt) mod sizeof(pointer))=0);
  pt:=pchar(ansistr);
  test((ptruint(pt) mod sizeof(pointer))=0);
{$ifdef haswidestring}
  pt:=pchar(widestr);
{$ifdef FPC_WINLIKEWIDESTRING}
  test((ptruint(pt) mod 4)=0);
{$else FPC_WINLIKEWIDESTRING}
  test((ptruint(pt) mod sizeof(pointer))=0);
{$endif FPC_WINLIKEWIDESTRING}
{$endif}
end.