# Legal ways to specify the leading clock in SVA

**URL:** <https://verificationacademy.com/forums/t/legal-ways-to-specify-the-leading-clock-in-sva/42485>\
**Category:** SystemVerilog\
**Tags:** SystemVerilog, Legal-ways-to-specify-the-leading-clock-in-SVA\
**Created:** [October 1, 2023, 11:30am UTC](https://verificationacademy.com/forums/t/legal-ways-to-specify-the-leading-clock-in-sva/42485 "2023-10-01T11:30:40Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![user49](https://verificationacademy.com/forums/user_avatar/verificationacademy.com/user49/32/1084_2.png) [@user49](https://verificationacademy.com/forums/u/user49)\
**Post date:** [October 7, 2023, 8:57pm UTC](https://verificationacademy.com/forums/t/legal-ways-to-specify-the-leading-clock-in-sva/42485/11 "2023-10-07T20:57:05Z")

</div>

_In reply to [Have\_A\_Doubt](https://verificationacademy.com/forums/t/legal-ways-to-specify-the-leading-clock-in-sva/42485/10):_

1800 16.16 and 16.16.1 exhaustively go thru al the rules for inferred leading clocking event (LCE). It is tiresome to read and fully comprehend. Byt in simple terms, and as a guideline, if the property does not have a clocking event then the inferred LCE is only in an always in the style of **always @(clocing\_event)**  
Just stick to this rule if you do not want to include the clocking event in the assertion.  
You’re making life too complicated if you violate simple design rules; and that is true for SV in general. Funky stuff can lead to funky behavior.  
Ben

---

_[View the full topic](https://verificationacademy.com/forums/t/legal-ways-to-specify-the-leading-clock-in-sva/42485)._
