mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-20 19:42:54 +02:00
19d53b6f8f
Most of the handling is pretty straightforward; fetch the default memory flags for the specific resource type before parsing the flags and apply them on top of that, except that some flags imply others and some flags clear more than one flag. For icons and cursors, the flags set get passed on to all individual single icon/cursor resources, while only some flags affect the icon/cursor group resource. For stringtables, the behaviour is pretty simple; the first stringtable resource of a bundle sets the flags for the whole bundle. The output of these tests match rc.exe byte for byte. The actual use of these memory flags is deprecated and they have no effect since Win16, but some resource script files may still happen to have them in place. Differential Revision: https://reviews.llvm.org/D46818 llvm-svn: 332329
29 lines
459 B
Plaintext
29 lines
459 B
Plaintext
// Flags set on the first stringtable of a bundle gets set
|
|
STRINGTABLE IMPURE {
|
|
0 "a"
|
|
}
|
|
|
|
// and end up in effect over whatever data is added here.
|
|
STRINGTABLE
|
|
{
|
|
1 "b"
|
|
}
|
|
|
|
STRINGTABLE
|
|
LANGUAGE 4, 7 {
|
|
2 "c"
|
|
}
|
|
|
|
// Flags set on a later stringtable as part of an earlier bundle
|
|
// have no effect.
|
|
STRINGTABLE FIXED PRELOAD
|
|
LANGUAGE 4, 7 {
|
|
3 "d"
|
|
}
|
|
|
|
// While the same flag on a new bundle does have effect.
|
|
STRINGTABLE FIXED PRELOAD
|
|
LANGUAGE 4, 8 {
|
|
4 "e"
|
|
}
|