---- Reported by faceprint@faceprint.com 2006-07-30 15:31:23 MST ----

Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:

Compile the attached .cs file with GMCS.  The Invalid function produces
invalid IL, while the Valid function, which does the same thing a little
more explicitly, produces valid IL.


Steps to reproduce the problem:
1. Compile the attached .cs
2. Look at the IL generated.

Actual Results:
Invalid IL is generated for the Invalid function.


Expected Results:
Valid IL (very similar if not identical to the IL for the Valid function)
should be generated for the Invalid function.


How often does this happen? 
Every time.


Additional Information:
I've reproduced this with gmcs 1.1.16.1 on a Linux box, 1.1.14.0 on a win32
box, and 1.1.13.2 on a solaris box.



---- Additional Comments From faceprint@faceprint.com 2006-07-30 15:32:24 MST ----

Created an attachment (id=170188)
C# source code demonstrating bug.




---- Additional Comments From miguel@ximian.com 2006-10-07 11:43:48 MST ----

Peverify reports:
quack$ peverify inv.exe

Microsoft (R) .NET Framework PE Verifier.  Version  2.0.50727.42
Copyright (c) Microsoft Corporation.  All rights reserved.

[IL]: Error: [C:\cygwin\home\miguel\inv.exe :
Testcase`1[T]::Invalid][offset 0x0000000F][found address of ref ]
Unexpected type on the stack.
1 Error Verifying inv.exe



---- Additional Comments From martin@ximian.com 2006-10-09 09:41:47 MST ----

Fixed in SVN; added gtest-293.cs.

Imported an attachment (id=170188)

Unknown bug field "cf_op_sys_details" encountered while moving bug
   <cf_op_sys_details>Ubuntu 6.06 + mono 1.1.16.1</cf_op_sys_details>