vishapoberon/compiler
1
0
Fork 0
mirror of https://github.com/vishapoberon/compiler.git synced 2026-04-06 16:52:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

updated hints file with known bug about shifting variables of set type

Browse source 
Former-commit-id: 80a34fe70c
This commit is contained in:
Norayr Chilingarian 2013-10-30 21:47:34 +04:00
parent 514f908bda
commit d6f0482c2e
1 changed files with 5 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
hints
View file

@ -24,3 +24,8 @@ set your BOOLEAN value in OPM.OpenPari (or in ScanOptions, after the CASE) so yo
check your boolean when necessary, (see useParFile in OPM.GetOptions) check your boolean when necessary, (see useParFile in OPM.GetOptions)
add it in OPC.GenHeaderMsg function. add it in OPC.GenHeaderMsg function.
==known bugs==
when SYSTEM.LSH(s, n) where s is SET c compiler generates an error: "error: duplicate 'unsigned'", that's because SET is defined as unsigned already and LSH is defined in SYSTEM.h as ((t)((unsigned t)(x)<<(n))), that's why currently it's not possible to make SYSTEM.LSH with type SET.
I don't want to prohibit it at the parser level because C backend is only one of possible backends.
The solution currently is to cast set type to longint before lsh-ing it. And then casting it back to set if necessary.