Difference: CompilerIssues (1 vs. 3)

Revision 32008-02-11 - KirkKelsey

Line: 1 to 1
 
META TOPICPARENT name="CompilerRepository"

Pending

  • The compiler should check to ensure that the optimization flag is set when the bop option is used. Otherwise the compiler seg. fault and the user is nonplussed. added by ChenDing - 31 Jan 2008.
  • When global variables are moved by GccMonk, the allocation should properly cast the return type (to avoid potential warnings). -- KirkKelsey - 04 Feb 2008
\ No newline at end of file
Added:
>
>
  • Finish some of the corner cases in Monk's bop-inst.c (asserts where we don't know what to do)
    • line 2266: causes compilation failure for the stdarg and init tests (from /p/compiler/lcc/tst/)
    • line 3042: causes compilation failure for the struct and paranoia tests (from /p/compiler/lcc/tst/)

Revision 22008-02-04 - KirkKelsey

Line: 1 to 1
 
META TOPICPARENT name="CompilerRepository"
Deleted:
<
<
 

Pending

  • The compiler should check to ensure that the optimization flag is set when the bop option is used. Otherwise the compiler seg. fault and the user is nonplussed. added by ChenDing - 31 Jan 2008.
\ No newline at end of file
Line: 4 to 3
 

Pending

  • The compiler should check to ensure that the optimization flag is set when the bop option is used. Otherwise the compiler seg. fault and the user is nonplussed. added by ChenDing - 31 Jan 2008.
\ No newline at end of file
Added:
>
>
  • When global variables are moved by GccMonk, the allocation should properly cast the return type (to avoid potential warnings). -- KirkKelsey - 04 Feb 2008
 \ No newline at end of file

Revision 12008-01-31 - ChenDing

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="CompilerRepository"

Pending

  • The compiler should check to ensure that the optimization flag is set when the bop option is used. Otherwise the compiler seg. fault and the user is nonplussed. added by ChenDing - 31 Jan 2008.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding URCS? Send feedback