From: Moore, Robert <robert.moore at intel.com>
To: devel@acpica.org
Subject: Re: [Devel] Field Offset constraints
Date: Wed, 03 Apr 2019 19:07:57 +0000 [thread overview]
Message-ID: <94F2FBAB4432B54E8AACC7DFDE6C92E3B95770C9@ORSMSX110.amr.corp.intel.com> (raw)
In-Reply-To: CAE-gjdXB9sWnBvdwuWNp+y-m3AFoDznvTy9sPbyO_qsTVyYs0Q@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
We do in fact keep tightening up the compiler to check for semantic issues as well as syntax errors. As it stands today, we have 164 errors/warnings/remarks, as well as 13 additional errors for the Data Table compiler, and 11 errors for the preprocessor.
Do you have any additional suggestions?
Bob
From: Patrick Georgi [mailto:pgeorgi(a)google.com]
Sent: Wednesday, April 3, 2019 11:08 AM
To: Moore, Robert <robert.moore(a)intel.com>
Cc: devel(a)acpica.org; Schmauss, Erik <erik.schmauss(a)intel.com>
Subject: Re: [Devel] Field Offset constraints
Hi Robert,
Am Mi., 3. Apr. 2019 um 19:38 Uhr schrieb Moore, Robert <robert.moore(a)intel.com<mailto:robert.moore(a)intel.com>>:
2) Disable the specific remark via the –VW option.
iasl -vw 2158 dsdt.asl // disable remark #2158
Thank you for the pointer to that option, that's very helpful.
Independent from that, is there interest in providing language features on top of ASL (maybe in revisions to the spec if the tool is meant to remain strictly compliant) to more rigorously express constraints that can be verified at compile time?
Regards,
Patrick
--
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5829 bytes --]
next reply other threads:[~2019-04-03 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 19:07 Moore, Robert [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-05 19:16 [Devel] Field Offset constraints Moore, Robert
2019-04-04 20:35 Patrick Georgi
2019-04-04 20:12 Schmauss, Erik
2019-04-03 21:51 Patrick Georgi
2019-04-03 21:26 Schmauss, Erik
2019-04-03 18:07 Patrick Georgi
2019-04-03 17:38 Moore, Robert
2019-04-03 7:14 Patrick Georgi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94F2FBAB4432B54E8AACC7DFDE6C92E3B95770C9@ORSMSX110.amr.corp.intel.com \
--to=devel@acpica.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.