<@U0172QZ342D> it is not a problem in the libs.ref...
# sky130
s
@User it is not a problem in the libs.ref generation, i see the same in the source files:
skywater-pdk/libraries/sky130_fd_sc_hd/latest/cells/dlxb/sky130_fd_sc_hd__dlxbn.behavioral.v
.
Copy code
`celldefine
module sky130_fd_sc_hd__dlxbn (
    Q     ,
    Q_N   ,
    D     ,
    GATE_N
);

    // Module ports
    output Q     ;
    output Q_N   ;
    input  D     ;
    input  GATE_N;

    // Module supplies
    supply1 VPWR;
    supply0 VGND;
    supply1 VPB ;
    supply0 VNB ;

    // Local signals
    wire GATE          ;
    wire buf_Q         ;
    wire GATE_N_delayed;
    wire D_delayed     ;
    reg  notifier      ;
    wire awake         ;
    wire 1             ;

    //                                    Name     Output  Other arguments
    not                                   not0    (GATE  , GATE_N_delayed                       );
    sky130_fd_sc_hd__udp_dlatch$P_pp$PG$N dlatch0 (buf_Q , D_delayed, GATE, notifier, VPWR, VGND);
    assign awake = ( VPWR === 1 );
    buf                                   buf0    (Q     , buf_Q                                );
    not                                   not1    (Q_N   , buf_Q                                );

endmodule
`endcelldefine
Clearly '1' is not a valid identifier in Verilog (as well as in most programming/HDL languages). I also can not understand how
GATE_N_delayed
,
notifier
and
D_delayed
are generated, there are probably some macros or included files that take care of these signals?.