Move optimizer to linq4j, improve translation of strict functions

[vlsi]

No description provided.

[vlsi]

Here is the updated PR.

Notable improvements:

1. Shortcut in CAST translation: when source type is equal to target type, avoid code generation (it used to generate things like bool == null ? null : bool)
2. NullAs support for CASE. I've identified that lots of inefficiencies in generated code are due to improper case translation: case ... end IS NULL should pass is null inside to optimize the check (i.e. use unboxed primitives, STRICT optimizations, etc)

[julianhyde]

Thanks! As I said on the optiq-dev list, I'll release linq4j in the next
few days, including all of your recent PRs, then merge this optiq PR.

On Sat, Apr 19, 2014 at 2:06 PM, Vladimir Sitnikov <notifications@github.com

wrote:

Here is the updated PR.

Notable improvements:

1. Shortcut in CAST translation: when source type is equal to target
   type, avoid code generation (it used to generate things like bool == null
   ? null : bool)
2. NullAs support for CASE. I've identified that lots of inefficiencies
   in generated code are due to improper case translation: case ... end IS
   NULL should pass is null inside to optimize the check (i.e. use unboxed
   primitives, STRICT optimizations, etc)

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/249#issuecomment-40880711
.

[julianhyde]

Rebased as cff9fb0.