Error when generating an obj file and using -O jit

[winksaville]

Describe the bug Error generating an obj file when using -O jit, it looks to be related to the new polygon shape. There was no issue when I used a rect. Also, as shown below, without -O jit the tri.curv programed worked.

Curv Program

$ cat tri.curv
polygon [[-5, 0], [0, 10], [5, 0]]
>> extrude 20

To Reproduce run curv with -O jit on the above program

$ curv -o tri.obj -O jit tri.curv
/home/wink/prgs/curv3d/projects/polygons/,curv-147910-0.cpp: In function ‘void dist(const vec4*, float*)’:
/home/wink/prgs/curv3d/projects/polygons/,curv-147910-0.cpp:74:15: error: no match for ‘operator!’ (operand type is ‘glm::bvec3’ {aka ‘glm::vec<3, bool, glm::packed_highp>’})
   74 |   bvec3 r58 = not(r52);
      |               ^~~~~~~~
/home/wink/prgs/curv3d/projects/polygons/,curv-147910-0.cpp:74:15: note: candidate: ‘operator!(bool)’ (built-in)
/home/wink/prgs/curv3d/projects/polygons/,curv-147910-0.cpp:74:15: note:   no known conversion for argument 1 from ‘glm::bvec3’ {aka ‘glm::vec<3, bool, glm::packed_highp>’} to ‘bool’
ERROR: c++ compile failed; see "/home/wink/prgs/curv3d/projects/polygons/,curv-147910-0.cpp"

Without -O jit it works and I was able to view the tri.obj in prusa-slicer:

$ curv -o tri.obj tri.curv
You are in SLOW MODE. Use '-O jit' to speed up rendering.
vsize=0.271442: 43×42×79 voxels. Use '-O vsize=N' to change voxel size.
Rendered 142674 voxels in 2.00806s (71050 voxels/s).
12702 quads.

Expected behavior No error when using -O jit

System Information (please complete the following information):

• Operating System:

  $ uname -a
  Linux 3900x 5.7.2-arch1-1 #1 SMP PREEMPT Wed, 10 Jun 2020 20:36:24 +0000 x86_64 GNU/Linux

• CPU manufacturer, model, version, and # of cores:

  $ lscpu
  Architecture:                    x86_64
  CPU op-mode(s):                  32-bit, 64-bit
  Byte Order:                      Little Endian
  Address sizes:                   43 bits physical, 48 bits virtual
  CPU(s):                          24
  On-line CPU(s) list:             0-23
  Thread(s) per core:              2
  Core(s) per socket:              12
  Socket(s):                       1
  NUMA node(s):                    1
  Vendor ID:                       AuthenticAMD
  CPU family:                      23
  Model:                           113
  Model name:                      AMD Ryzen 9 3900X 12-Core Processor
  Stepping:                        0
  Frequency boost:                 enabled
  CPU MHz:                         2481.323
  CPU max MHz:                     3800.0000
  CPU min MHz:                     2200.0000
  BogoMIPS:                        7603.68
  Virtualization:                  AMD-V
  L1d cache:                       384 KiB
  L1i cache:                       384 KiB
  L2 cache:                        6 MiB
  L3 cache:                        64 MiB
  NUMA node0 CPU(s):               0-23
  Vulnerability Itlb multihit:     Not affected
  Vulnerability L1tf:              Not affected
  Vulnerability Mds:               Not affected
  Vulnerability Meltdown:          Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
  Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Vulnerability Spectre v2:        Mitigation; Full AMD retpoline, IBPB conditional, STIBP conditional, RSB filling
  Vulnerability Srbds:             Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_g
                               ood nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic 
                               cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate sme ssbd
                                mba sev ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_tota
                               l cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic
                                v_vmsave_vmload vgif umip rdpid overflow_recov succor smca

• Amount of system memory:

  $ vmstat -s
   32807276 K total memory
    7165968 K used memory
    8142412 K active memory
    5545572 K inactive memory
   17839404 K free memory
     779188 K buffer memory
    7022716 K swap cache
          0 K total swap
          0 K used swap
          0 K free swap
    8634556 non-nice user cpu ticks
  227676580 nice user cpu ticks
   74122988 system cpu ticks
  187866704 idle cpu ticks
     369497 IO-wait cpu ticks
     712542 IRQ cpu ticks
     230259 softirq cpu ticks
          0 stolen cpu ticks
    7108129 pages paged in
   52817553 pages paged out
          0 pages swapped in
          0 pages swapped out
  1365302534 interrupts
  2671828802 CPU context switches
  1591972720 boot time
     149027 forks

• GPU manufacturer, model and version: See Curv Version
• GPU driver, if on Linux:See Curv Version
• Are you running the curv command using a remote viewing protocol like VNC or NX? NO
• Are you running the curv command inside a VM? NO
• Curv Version: run the command curv --version:

  $ curv --version
  Curv: 0.4-628-g04d9e73f
  Compiler: gcc 10.1.0
  Kernel: Linux 5.7.2-arch1-1 x86_64
  GPU: NVIDIA Corporation, GeForce GTX 1660/PCIe/SSE2
  OpenGL: 4.6.0 NVIDIA 440.82

Additional context Add any other context about the problem here.

[doug-moen]

Thanks!

[winksaville]

FYI: Something I discovered very recently. You can link pull requests "automatically" to issues which can be handy as the person who created the issue will see what commit fixed it.

On Sun, Jun 14, 2020, 6:39 PM Doug Moen notifications@github.com wrote:

Closed #94 https://github.com/curv3d/curv/issues/94.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/curv3d/curv/issues/94#event-3442282761, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH2CHBQQR75MH2KI5IC5CLRWV3VRANCNFSM4N5WJBAA .

[winksaville]

Whoops, here is the link: https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue

On Sun, Jun 14, 2020, 7:06 PM Wink Saville wink@saville.com wrote:

FYI: Something I discovered very recently. You can link pull requests "automatically" to issues which can be handy as the person who created the issue will see what commit fixed it.

On Sun, Jun 14, 2020, 6:39 PM Doug Moen notifications@github.com wrote:

Closed #94 https://github.com/curv3d/curv/issues/94.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/curv3d/curv/issues/94#event-3442282761, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH2CHBQQR75MH2KI5IC5CLRWV3VRANCNFSM4N5WJBAA .

[doug-moen]

Thanks, I'll try this next time.

[winksaville]

Cool, I've used "Fixes #XX" in the last "paragraph" on another repo and seemed to work.

On Mon, Jun 15, 2020, 5:22 PM Doug Moen notifications@github.com wrote:

Thanks, I'll try this next time.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/curv3d/curv/issues/94#issuecomment-644458037, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH2CHEDIBWQ3MUARJK5SDLRW23NHANCNFSM4N5WJBAA .