* [Devel] ACPICA version 20130927 released
@ 2013-09-27 16:59 Moore, Robert
0 siblings, 0 replies; 10+ messages in thread
From: Moore, Robert @ 2013-09-27 16:59 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 5012 bytes --]
27 September 2013. Summary of changes for version 20130927:
This release is available at https://acpica.org/downloads
1) ACPICA kernel-resident subsystem:
Fixed a problem with store operations to reference objects. This change fixes a problem where a Store operation to an ArgX object that contained a reference to a field object did not complete the automatic dereference and then write to the actual field object. Instead, the object type of the field object was inadvertently changed to match the type of the source operand. The new behavior will actually write to the field object (buffer field or field unit), thus matching the correct ACPI-defined behavior.
Implemented support to allow the host to redefine individual OSL prototypes. This change enables the host to redefine OSL prototypes found in the acpiosxf.h file. This allows the host to implement OSL interfaces with a macro or inlined function. Further, it allows the host to add any additional required modifiers such as __iomem, __init, __exit, etc., as necessary on a per-interface basis. Enables maximum flexibility for the OSL interfaces. Lv Zheng.
Hardcoded the access width for the FADT-defined reset register. The ACPI specification requires the reset register width to be 8 bits. ACPICA now hardcodes the width to 8 and ignores the FADT width value. This provides compatibility with other ACPI implementations that have allowed BIOS code with bad register width values to go unnoticed. Matthew Garett, Bob Moore, Lv Zheng.
Changed the position/use of the ACPI_PRINTF_LIKE macro. This macro is used in the OSL header (acpiosxf). The change modifies the position of this macro in each instance where it is used (AcpiDebugPrint, etc.) to avoid build issues if the OSL defines the implementation of the interface to be an inline stub function. Lv Zheng.
Deployed a new macro ACPI_EXPORT_SYMBOL_INIT for the main ACPICA initialization interfaces. This change adds a new macro for the main init and terminate external interfaces in order to support hosts that require additional or different processing for these functions. Changed from ACPI_EXPORT_SYMBOL to ACPI_EXPORT_SYMBOL_INIT for these functions. Lv Zheng, Bob Moore.
Cleaned up the memory allocation macros for configurability. In the common case, the ACPI_ALLOCATE and related macros now resolve directly to their respective AcpiOs* OSL interfaces. Two options:
1) The ACPI_ALLOCATE_ZEROED macro uses a simple local implementation by default, unless overridden by the USE_NATIVE_ALLOCATE_ZEROED define.
2) For AcpiExec (and for debugging), the macros can optionally be resolved to the local ACPICA interfaces that track each allocation (local tracking is used to immediately detect memory leaks).
Lv Zheng.
Simplified the configuration for ACPI_REDUCED_HARDWARE. Allows the kernel to predefine this macro to either TRUE or FALSE during the system build.
Replaced __FUNCTION_ with __func__ in the gcc-specific header.
Example Code and Data Size: These are the sizes for the OS-independent acpica.lib produced by the Microsoft Visual C++ 9.0 32-bit compiler. The debug version of the code includes the debug output trace mechanism and has a much larger code and data size.
Current Release:
Non-Debug Version: 95.8K Code, 27.0K Data, 122.8K Total
Debug Version: 185.2K Code, 77.2K Data, 262.4K Total
Previous Release:
Non-Debug Version: 96.7K Code, 27.1K Data, 123.9K Total
Debug Version: 184.4K Code, 76.8K Data, 261.2K Total
2) iASL Compiler/Disassembler and Tools:
iASL: Implemented wildcard support for the -e option. This simplifies use when there are many SSDTs that must be included to resolve external method declarations. ACPICA BZ 1041. Example:
iasl -e ssdt*.dat -d dsdt.dat
AcpiExec: Add history/line-editing for Unix/Linux systems. This change adds a portable module that implements full history and limited line editing for Unix and Linux systems. It does not use readline() due to portability issues. Instead it uses the POSIX termio interface to put the terminal in raw input mode so that the various special keys can be trapped (such as up/down-arrow for history support and left/right-arrow for line editing). Uses the existing debugger history mechanism. ACPICA BZ 1036.
AcpiXtract: Add support to handle (ignore) "empty" lines containing only one or more spaces. This provides compatible with early or different versions of the AcpiDump utility. ACPICA BZ 1044.
AcpiDump: Do not ignore tables that contain only an ACPI table header. Apparently, some BIOSs create SSDTs that contain an ACPI table header but no other data. This change adds support to dump these tables. Any tables shorter than the length of an ACPI table header remain in error (an error message is emitted). Reported by Yi Li.
Debugger: Echo actual command along with the "unknown command" message.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 8940 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Devel] ACPICA version 20130927 released
@ 2013-09-30 17:11 Jung-uk Kim
0 siblings, 0 replies; 10+ messages in thread
From: Jung-uk Kim @ 2013-09-30 17:11 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2013-09-27 12:59:34 -0400, Robert Moore wrote:
> 27 September 2013. Summary of changes for version 20130927:
...
Unfortunately, there are two regressions with the release. First, the
release tarballs are missing Makefile.config:
% tar tfv acpica-unix-20130927.tar.gz | grep generate/unix/Makefile
- -rw-r--r-- 0 rmoore1 Domain Users 543 9 27 12:18
acpica-unix-20130927/generate/unix/Makefile
- -rw-r--r-- 0 rmoore1 Domain Users 2057 9 27 12:18
acpica-unix-20130927/generate/unix/Makefile.common
- -rw-r--r-- 0 rmoore1 Domain Users 519 9 27 12:18
acpica-unix-20130927/generate/unix/Makefile.rules
% tar tfv acpica-unix2-20130927.tar.gz | grep generate/unix/Makefile
- -rw-r--r-- 0 rmoore1 Domain Users 543 9 27 12:18
acpica-unix2-20130927/generate/unix/Makefile
- -rw-r--r-- 0 rmoore1 Domain Users 2057 9 27 12:18
acpica-unix2-20130927/generate/unix/Makefile.common
- -rw-r--r-- 0 rmoore1 Domain Users 519 9 27 12:18
acpica-unix2-20130927/generate/unix/Makefile.rules
Even after adding the file from github, I realized this release does
not support traditional yacc any more and now it only builds with GNU
bison since this commit:
https://github.com/acpica/acpica/commit/d8a0e964
Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)
iQEcBAEBAgAGBQJSSbC4AAoJEHyflib82/FGuKYH/jmdm/vsgq2svgHIrIzJBK7R
GDkHtJjpNNGXIh7+OGndoodQCIesyXPfd1NOKYIww8S8ScO80vAJ0eK/qx2dkJUU
ZPtgiAgZkgU/S413OXIa6FDd1sdV1gOMOiIEIc6NeCgyOr+L3pxzVsrN2/KNgymH
8XnRtP7svnNatrpv8bWl48PX1VT2Vxe6ZlXJSh7jbz0YG5cAqQ+ycnKiZBmpHtId
v92aDFKbbqXg8nOYJcpqFCsxr+dlQtcUxPLfYyzo0q1jK4kTRjGsus1eDk6BEJuP
u9TpyRV9V9wj3s/G5JPV4sFJpeoOHXLqoavHypipima8fherg8ATBDP240juiM4=
=SGYi
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Devel] ACPICA version 20130927 released
@ 2013-09-30 17:40 Jung-uk Kim
0 siblings, 0 replies; 10+ messages in thread
From: Jung-uk Kim @ 2013-09-30 17:40 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2013-09-30 13:11:21 -0400, Jung-uk Kim wrote:
> On 2013-09-27 12:59:34 -0400, Robert Moore wrote:
>> 27 September 2013. Summary of changes for version 20130927:
> ... Unfortunately, there are two regressions with the release.
> First, the release tarballs are missing Makefile.config:
>
> % tar tfv acpica-unix-20130927.tar.gz | grep
> generate/unix/Makefile -rw-r--r-- 0 rmoore1 Domain Users 543 9
> 27 12:18 acpica-unix-20130927/generate/unix/Makefile -rw-r--r-- 0
> rmoore1 Domain Users 2057 9 27 12:18
> acpica-unix-20130927/generate/unix/Makefile.common -rw-r--r-- 0
> rmoore1 Domain Users 519 9 27 12:18
> acpica-unix-20130927/generate/unix/Makefile.rules % tar tfv
> acpica-unix2-20130927.tar.gz | grep generate/unix/Makefile
> -rw-r--r-- 0 rmoore1 Domain Users 543 9 27 12:18
> acpica-unix2-20130927/generate/unix/Makefile -rw-r--r-- 0 rmoore1
> Domain Users 2057 9 27 12:18
> acpica-unix2-20130927/generate/unix/Makefile.common -rw-r--r-- 0
> rmoore1 Domain Users 519 9 27 12:18
> acpica-unix2-20130927/generate/unix/Makefile.rules
>
> Even after adding the file from github, I realized this release
> does not support traditional yacc any more and now it only builds
> with GNU bison since this commit:
>
> https://github.com/acpica/acpica/commit/d8a0e964
BTW, FreeBSD had a similar problem in the past and we worked around it
like this:
http://svnweb.freebsd.org/changeset/base/232676
I am sure GNU make gurus should be able to do something similar
without breaking yacc support. ;-)
Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)
iQEcBAEBAgAGBQJSSbeCAAoJEHyflib82/FGqiIH/RullH+KMkBKsQ3u8efR0TbV
hf8CW37fQH6CNLVZnBRT7o6Jgv+ot4ChZA+Rj6nLmHWc2jHr6b+JsKjLFENW7o9V
I+4NAFvEpl1sJFMkw6IczTFS1kmiuaB3eNyLK9bGKqS9clku9mT6vjMP6uTc+arn
aze9Sa8f5stLRjjg3A/DKVAztATTT7Dsb2m1OGgILPdZju03PNe8U1DhF1LyzmYw
0IJS10U6rJe4CFTeIz2LKyc8mfTe1CE2Sao7pWqFRgHqf9bOcl6Wbd4gCkCQpPsT
Fa0voEiLexD3yuUdwihfRWuhQy14UNaa8Nw1FpA6skQ+H70zExsdBMQyQmjGsSg=
=v2xf
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Devel] ACPICA version 20130927 released
@ 2013-09-30 22:28 Zheng, Lv
0 siblings, 0 replies; 10+ messages in thread
From: Zheng, Lv @ 2013-09-30 22:28 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 2551 bytes --]
OK, the regression is introduced by my commit.
I can take a look at this issue.
Could you send me the version and usage of yacc you are using.
It is better that you can post "yacc -v" and "yacc -h" for me.
Thanks and best regards
-Lv
> -----Original Message-----
> From: devel-bounces(a)acpica.org [mailto:devel-bounces(a)acpica.org] On Behalf Of Jung-uk Kim
> Sent: Tuesday, October 01, 2013 1:11 AM
> To: Moore, Robert; devel(a)acpica.org
> Subject: Re: [Devel] ACPICA version 20130927 released
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2013-09-27 12:59:34 -0400, Robert Moore wrote:
> > 27 September 2013. Summary of changes for version 20130927:
> ...
> Unfortunately, there are two regressions with the release. First, the
> release tarballs are missing Makefile.config:
>
> % tar tfv acpica-unix-20130927.tar.gz | grep generate/unix/Makefile
> - -rw-r--r-- 0 rmoore1 Domain Users 543 9 27 12:18
> acpica-unix-20130927/generate/unix/Makefile
> - -rw-r--r-- 0 rmoore1 Domain Users 2057 9 27 12:18
> acpica-unix-20130927/generate/unix/Makefile.common
> - -rw-r--r-- 0 rmoore1 Domain Users 519 9 27 12:18
> acpica-unix-20130927/generate/unix/Makefile.rules
> % tar tfv acpica-unix2-20130927.tar.gz | grep generate/unix/Makefile
> - -rw-r--r-- 0 rmoore1 Domain Users 543 9 27 12:18
> acpica-unix2-20130927/generate/unix/Makefile
> - -rw-r--r-- 0 rmoore1 Domain Users 2057 9 27 12:18
> acpica-unix2-20130927/generate/unix/Makefile.common
> - -rw-r--r-- 0 rmoore1 Domain Users 519 9 27 12:18
> acpica-unix2-20130927/generate/unix/Makefile.rules
>
> Even after adding the file from github, I realized this release does
> not support traditional yacc any more and now it only builds with GNU
> bison since this commit:
>
> https://github.com/acpica/acpica/commit/d8a0e964
>
> Jung-uk Kim
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.21 (FreeBSD)
>
> iQEcBAEBAgAGBQJSSbC4AAoJEHyflib82/FGuKYH/jmdm/vsgq2svgHIrIzJBK7R
> GDkHtJjpNNGXIh7+OGndoodQCIesyXPfd1NOKYIww8S8ScO80vAJ0eK/qx2dkJUU
> ZPtgiAgZkgU/S413OXIa6FDd1sdV1gOMOiIEIc6NeCgyOr+L3pxzVsrN2/KNgymH
> 8XnRtP7svnNatrpv8bWl48PX1VT2Vxe6ZlXJSh7jbz0YG5cAqQ+ycnKiZBmpHtId
> v92aDFKbbqXg8nOYJcpqFCsxr+dlQtcUxPLfYyzo0q1jK4kTRjGsus1eDk6BEJuP
> u9TpyRV9V9wj3s/G5JPV4sFJpeoOHXLqoavHypipima8fherg8ATBDP240juiM4=
> =SGYi
> -----END PGP SIGNATURE-----
> _______________________________________________
> Devel mailing list
> Devel(a)acpica.org
> https://lists.acpica.org/mailman/listinfo/devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Devel] ACPICA version 20130927 released
@ 2013-09-30 22:50 Zheng, Lv
0 siblings, 0 replies; 10+ messages in thread
From: Zheng, Lv @ 2013-09-30 22:50 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 3058 bytes --]
Hi, Kim
I took a look at the Makefile you are using.
It seems the problem is that the "--defines" is not supported by the traditional yacc.
I can see you are using .ORDER and empty touch to solve issues that can be solved by --defines.
So my question is:
1. Shall we still support traditional yacc?
2. Are there any better way other than using the ugly empty "touch"?
Thanks and best regards
-Lv
> -----Original Message-----
> From: devel-bounces(a)acpica.org [mailto:devel-bounces(a)acpica.org] On Behalf Of Jung-uk Kim
> Sent: Tuesday, October 01, 2013 1:40 AM
> To: Moore, Robert; devel(a)acpica.org
> Subject: Re: [Devel] ACPICA version 20130927 released
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2013-09-30 13:11:21 -0400, Jung-uk Kim wrote:
> > On 2013-09-27 12:59:34 -0400, Robert Moore wrote:
> >> 27 September 2013. Summary of changes for version 20130927:
> > ... Unfortunately, there are two regressions with the release.
> > First, the release tarballs are missing Makefile.config:
> >
> > % tar tfv acpica-unix-20130927.tar.gz | grep
> > generate/unix/Makefile -rw-r--r-- 0 rmoore1 Domain Users 543 9
> > 27 12:18 acpica-unix-20130927/generate/unix/Makefile -rw-r--r-- 0
> > rmoore1 Domain Users 2057 9 27 12:18
> > acpica-unix-20130927/generate/unix/Makefile.common -rw-r--r-- 0
> > rmoore1 Domain Users 519 9 27 12:18
> > acpica-unix-20130927/generate/unix/Makefile.rules % tar tfv
> > acpica-unix2-20130927.tar.gz | grep generate/unix/Makefile
> > -rw-r--r-- 0 rmoore1 Domain Users 543 9 27 12:18
> > acpica-unix2-20130927/generate/unix/Makefile -rw-r--r-- 0 rmoore1
> > Domain Users 2057 9 27 12:18
> > acpica-unix2-20130927/generate/unix/Makefile.common -rw-r--r-- 0
> > rmoore1 Domain Users 519 9 27 12:18
> > acpica-unix2-20130927/generate/unix/Makefile.rules
> >
> > Even after adding the file from github, I realized this release
> > does not support traditional yacc any more and now it only builds
> > with GNU bison since this commit:
> >
> > https://github.com/acpica/acpica/commit/d8a0e964
>
> BTW, FreeBSD had a similar problem in the past and we worked around it
> like this:
>
> http://svnweb.freebsd.org/changeset/base/232676
>
> I am sure GNU make gurus should be able to do something similar
> without breaking yacc support. ;-)
>
> Jung-uk Kim
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.21 (FreeBSD)
>
> iQEcBAEBAgAGBQJSSbeCAAoJEHyflib82/FGqiIH/RullH+KMkBKsQ3u8efR0TbV
> hf8CW37fQH6CNLVZnBRT7o6Jgv+ot4ChZA+Rj6nLmHWc2jHr6b+JsKjLFENW7o9V
> I+4NAFvEpl1sJFMkw6IczTFS1kmiuaB3eNyLK9bGKqS9clku9mT6vjMP6uTc+arn
> aze9Sa8f5stLRjjg3A/DKVAztATTT7Dsb2m1OGgILPdZju03PNe8U1DhF1LyzmYw
> 0IJS10U6rJe4CFTeIz2LKyc8mfTe1CE2Sao7pWqFRgHqf9bOcl6Wbd4gCkCQpPsT
> Fa0voEiLexD3yuUdwihfRWuhQy14UNaa8Nw1FpA6skQ+H70zExsdBMQyQmjGsSg=
> =v2xf
> -----END PGP SIGNATURE-----
> _______________________________________________
> Devel mailing list
> Devel(a)acpica.org
> https://lists.acpica.org/mailman/listinfo/devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Devel] ACPICA version 20130927 released
@ 2013-09-30 22:54 Zheng, Lv
0 siblings, 0 replies; 10+ messages in thread
From: Zheng, Lv @ 2013-09-30 22:54 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 3369 bytes --]
> From: Zheng, Lv
> Sent: Tuesday, October 01, 2013 6:50 AM
>
> Hi, Kim
>
> I took a look at the Makefile you are using.
> It seems the problem is that the "--defines" is not supported by the traditional yacc.
> I can see you are using .ORDER and empty touch to solve issues that can be solved by --defines.
>
> So my question is:
> 1. Shall we still support traditional yacc?
> 2. Are there any better way other than using the ugly empty "touch"?
Sorry for the mistake.
It is ln, not a touch. Can it be eliminated using other means?
Thanks
-Lv
>
> Thanks and best regards
> -Lv
>
> > -----Original Message-----
> > From: devel-bounces(a)acpica.org [mailto:devel-bounces(a)acpica.org] On Behalf Of Jung-uk Kim
> > Sent: Tuesday, October 01, 2013 1:40 AM
> > To: Moore, Robert; devel(a)acpica.org
> > Subject: Re: [Devel] ACPICA version 20130927 released
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 2013-09-30 13:11:21 -0400, Jung-uk Kim wrote:
> > > On 2013-09-27 12:59:34 -0400, Robert Moore wrote:
> > >> 27 September 2013. Summary of changes for version 20130927:
> > > ... Unfortunately, there are two regressions with the release.
> > > First, the release tarballs are missing Makefile.config:
> > >
> > > % tar tfv acpica-unix-20130927.tar.gz | grep
> > > generate/unix/Makefile -rw-r--r-- 0 rmoore1 Domain Users 543 9
> > > 27 12:18 acpica-unix-20130927/generate/unix/Makefile -rw-r--r-- 0
> > > rmoore1 Domain Users 2057 9 27 12:18
> > > acpica-unix-20130927/generate/unix/Makefile.common -rw-r--r-- 0
> > > rmoore1 Domain Users 519 9 27 12:18
> > > acpica-unix-20130927/generate/unix/Makefile.rules % tar tfv
> > > acpica-unix2-20130927.tar.gz | grep generate/unix/Makefile
> > > -rw-r--r-- 0 rmoore1 Domain Users 543 9 27 12:18
> > > acpica-unix2-20130927/generate/unix/Makefile -rw-r--r-- 0 rmoore1
> > > Domain Users 2057 9 27 12:18
> > > acpica-unix2-20130927/generate/unix/Makefile.common -rw-r--r-- 0
> > > rmoore1 Domain Users 519 9 27 12:18
> > > acpica-unix2-20130927/generate/unix/Makefile.rules
> > >
> > > Even after adding the file from github, I realized this release
> > > does not support traditional yacc any more and now it only builds
> > > with GNU bison since this commit:
> > >
> > > https://github.com/acpica/acpica/commit/d8a0e964
> >
> > BTW, FreeBSD had a similar problem in the past and we worked around it
> > like this:
> >
> > http://svnweb.freebsd.org/changeset/base/232676
> >
> > I am sure GNU make gurus should be able to do something similar
> > without breaking yacc support. ;-)
> >
> > Jung-uk Kim
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.21 (FreeBSD)
> >
> > iQEcBAEBAgAGBQJSSbeCAAoJEHyflib82/FGqiIH/RullH+KMkBKsQ3u8efR0TbV
> > hf8CW37fQH6CNLVZnBRT7o6Jgv+ot4ChZA+Rj6nLmHWc2jHr6b+JsKjLFENW7o9V
> > I+4NAFvEpl1sJFMkw6IczTFS1kmiuaB3eNyLK9bGKqS9clku9mT6vjMP6uTc+arn
> > aze9Sa8f5stLRjjg3A/DKVAztATTT7Dsb2m1OGgILPdZju03PNe8U1DhF1LyzmYw
> > 0IJS10U6rJe4CFTeIz2LKyc8mfTe1CE2Sao7pWqFRgHqf9bOcl6Wbd4gCkCQpPsT
> > Fa0voEiLexD3yuUdwihfRWuhQy14UNaa8Nw1FpA6skQ+H70zExsdBMQyQmjGsSg=
> > =v2xf
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > Devel mailing list
> > Devel(a)acpica.org
> > https://lists.acpica.org/mailman/listinfo/devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Devel] ACPICA version 20130927 released
@ 2013-10-01 18:25 Jung-uk Kim
0 siblings, 0 replies; 10+ messages in thread
From: Jung-uk Kim @ 2013-10-01 18:25 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2013-09-30 18:50:21 -0400, Lv Zheng wrote:
> Hi, Kim
>
> I took a look at the Makefile you are using. It seems the problem
> is that the "--defines" is not supported by the traditional yacc. I
> can see you are using .ORDER and empty touch to solve issues that
> can be solved by --defines.
>
> So my question is: 1. Shall we still support traditional yacc?
We tried hard not to break POSIX Yacc support for maximum
compatibility. In fact, I believe all *.y files were written for
POSIX Yacc and '-y' option was used for Bison to emulate POSIX Yacc.
GNU did not take over the world yet. ;-)
> 2. Are there any better way other than using the ugly empty
> "touch"?
I don't know if there's any easy way, unfortunately.
BTW, "-o/dev/null --defines=..." looks more hackish to my eyes but it
may be just me. :-p
Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)
iQEcBAEBAgAGBQJSSxOMAAoJEHyflib82/FGEacH+wfPhh+HNvt448L0W0tRd329
5RABk2PgK0ijWhsxEszz92bAIGqs4NXhpR44l8D4grfWaIYVWpGXjeVi0T/uz7Ca
oVu+U9yDHCBJcmftWe13Qg++oaujWZcpaSPC5vvc+mlbhcl+91ldk2cJ7ImAhN2E
PBwmikGuy+iioeZTbY+d7sZEMX55d0ZmXpR4PVT1udPwSq0PkLnRsT6GO+3vXamx
RKaq35U/aQFelyRfFA3d63pHOdA+tACsBNpuR/em/hQHYJwNTm7xY+vmy+rI5y2S
YJ6i7fh5mgfq8fUINq6Kpn12sKAhRi3L9U7Mfu0+pT1Qw3TQl0hd1qYhhsBk1UE=
=CVe9
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Devel] ACPICA version 20130927 released
@ 2013-10-01 22:42 Zheng, Lv
0 siblings, 0 replies; 10+ messages in thread
From: Zheng, Lv @ 2013-10-01 22:42 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
> From: Jung-uk Kim [mailto:jkim(a)FreeBSD.org]
> Sent: Wednesday, October 02, 2013 2:25 AM
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2013-09-30 18:50:21 -0400, Lv Zheng wrote:
> > Hi, Kim
> >
> > I took a look at the Makefile you are using. It seems the problem
> > is that the "--defines" is not supported by the traditional yacc. I
> > can see you are using .ORDER and empty touch to solve issues that
> > can be solved by --defines.
> >
> > So my question is: 1. Shall we still support traditional yacc?
>
> We tried hard not to break POSIX Yacc support for maximum
> compatibility. In fact, I believe all *.y files were written for
> POSIX Yacc and '-y' option was used for Bison to emulate POSIX Yacc.
> GNU did not take over the world yet. ;-)
>
Let Bob determine this.
> > 2. Are there any better way other than using the ugly empty
> > "touch"?
>
> I don't know if there's any easy way, unfortunately.
>
> BTW, "-o/dev/null --defines=..." looks more hackish to my eyes but it
> may be just me. :-p
>
:-) If POSIX yacc is going to be supported, I'll try again based on your idea.
Thanks for the report.
Cheers
-Lv
> Jung-uk Kim
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.21 (FreeBSD)
>
> iQEcBAEBAgAGBQJSSxOMAAoJEHyflib82/FGEacH+wfPhh+HNvt448L0W0tRd329
> 5RABk2PgK0ijWhsxEszz92bAIGqs4NXhpR44l8D4grfWaIYVWpGXjeVi0T/uz7Ca
> oVu+U9yDHCBJcmftWe13Qg++oaujWZcpaSPC5vvc+mlbhcl+91ldk2cJ7ImAhN2E
> PBwmikGuy+iioeZTbY+d7sZEMX55d0ZmXpR4PVT1udPwSq0PkLnRsT6GO+3vXamx
> RKaq35U/aQFelyRfFA3d63pHOdA+tACsBNpuR/em/hQHYJwNTm7xY+vmy+rI5y2S
> YJ6i7fh5mgfq8fUINq6Kpn12sKAhRi3L9U7Mfu0+pT1Qw3TQl0hd1qYhhsBk1UE=
> =CVe9
> -----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Devel] ACPICA version 20130927 released
@ 2013-10-01 22:56 Moore, Robert
0 siblings, 0 replies; 10+ messages in thread
From: Moore, Robert @ 2013-10-01 22:56 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 2151 bytes --]
Yes, I think the idea was to support Bison in "yacc compatibility" mode so that actual yacc could be used instead.
Bob
> -----Original Message-----
> From: Zheng, Lv
> Sent: Tuesday, October 01, 2013 3:42 PM
> To: Jung-uk Kim; Moore, Robert; devel(a)acpica.org
> Subject: RE: [Devel] ACPICA version 20130927 released
>
> > From: Jung-uk Kim [mailto:jkim(a)FreeBSD.org]
> > Sent: Wednesday, October 02, 2013 2:25 AM
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 2013-09-30 18:50:21 -0400, Lv Zheng wrote:
> > > Hi, Kim
> > >
> > > I took a look at the Makefile you are using. It seems the problem is
> > > that the "--defines" is not supported by the traditional yacc. I can
> > > see you are using .ORDER and empty touch to solve issues that can be
> > > solved by --defines.
> > >
> > > So my question is: 1. Shall we still support traditional yacc?
> >
> > We tried hard not to break POSIX Yacc support for maximum
> > compatibility. In fact, I believe all *.y files were written for
> > POSIX Yacc and '-y' option was used for Bison to emulate POSIX Yacc.
> > GNU did not take over the world yet. ;-)
> >
>
> Let Bob determine this.
>
> > > 2. Are there any better way other than using the ugly empty "touch"?
> >
> > I don't know if there's any easy way, unfortunately.
> >
> > BTW, "-o/dev/null --defines=..." looks more hackish to my eyes but it
> > may be just me. :-p
> >
>
> :-) If POSIX yacc is going to be supported, I'll try again based on your
> idea.
> Thanks for the report.
>
> Cheers
> -Lv
>
> > Jung-uk Kim
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.21 (FreeBSD)
> >
> > iQEcBAEBAgAGBQJSSxOMAAoJEHyflib82/FGEacH+wfPhh+HNvt448L0W0tRd329
> > 5RABk2PgK0ijWhsxEszz92bAIGqs4NXhpR44l8D4grfWaIYVWpGXjeVi0T/uz7Ca
> > oVu+U9yDHCBJcmftWe13Qg++oaujWZcpaSPC5vvc+mlbhcl+91ldk2cJ7ImAhN2E
> > PBwmikGuy+iioeZTbY+d7sZEMX55d0ZmXpR4PVT1udPwSq0PkLnRsT6GO+3vXamx
> > RKaq35U/aQFelyRfFA3d63pHOdA+tACsBNpuR/em/hQHYJwNTm7xY+vmy+rI5y2S
> > YJ6i7fh5mgfq8fUINq6Kpn12sKAhRi3L9U7Mfu0+pT1Qw3TQl0hd1qYhhsBk1UE=
> > =CVe9
> > -----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Devel] ACPICA version 20130927 released
@ 2013-10-02 16:15 Moore, Robert
0 siblings, 0 replies; 10+ messages in thread
From: Moore, Robert @ 2013-10-02 16:15 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 2066 bytes --]
Yes, I think we need to support yacc
> -----Original Message-----
> From: Zheng, Lv
> Sent: Tuesday, October 01, 2013 3:42 PM
> To: Jung-uk Kim; Moore, Robert; devel(a)acpica.org
> Subject: RE: [Devel] ACPICA version 20130927 released
>
> > From: Jung-uk Kim [mailto:jkim(a)FreeBSD.org]
> > Sent: Wednesday, October 02, 2013 2:25 AM
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 2013-09-30 18:50:21 -0400, Lv Zheng wrote:
> > > Hi, Kim
> > >
> > > I took a look at the Makefile you are using. It seems the problem is
> > > that the "--defines" is not supported by the traditional yacc. I can
> > > see you are using .ORDER and empty touch to solve issues that can be
> > > solved by --defines.
> > >
> > > So my question is: 1. Shall we still support traditional yacc?
> >
> > We tried hard not to break POSIX Yacc support for maximum
> > compatibility. In fact, I believe all *.y files were written for
> > POSIX Yacc and '-y' option was used for Bison to emulate POSIX Yacc.
> > GNU did not take over the world yet. ;-)
> >
>
> Let Bob determine this.
>
> > > 2. Are there any better way other than using the ugly empty "touch"?
> >
> > I don't know if there's any easy way, unfortunately.
> >
> > BTW, "-o/dev/null --defines=..." looks more hackish to my eyes but it
> > may be just me. :-p
> >
>
> :-) If POSIX yacc is going to be supported, I'll try again based on your
> idea.
> Thanks for the report.
>
> Cheers
> -Lv
>
> > Jung-uk Kim
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.21 (FreeBSD)
> >
> > iQEcBAEBAgAGBQJSSxOMAAoJEHyflib82/FGEacH+wfPhh+HNvt448L0W0tRd329
> > 5RABk2PgK0ijWhsxEszz92bAIGqs4NXhpR44l8D4grfWaIYVWpGXjeVi0T/uz7Ca
> > oVu+U9yDHCBJcmftWe13Qg++oaujWZcpaSPC5vvc+mlbhcl+91ldk2cJ7ImAhN2E
> > PBwmikGuy+iioeZTbY+d7sZEMX55d0ZmXpR4PVT1udPwSq0PkLnRsT6GO+3vXamx
> > RKaq35U/aQFelyRfFA3d63pHOdA+tACsBNpuR/em/hQHYJwNTm7xY+vmy+rI5y2S
> > YJ6i7fh5mgfq8fUINq6Kpn12sKAhRi3L9U7Mfu0+pT1Qw3TQl0hd1qYhhsBk1UE=
> > =CVe9
> > -----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2013-10-02 16:15 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-30 17:11 [Devel] ACPICA version 20130927 released Jung-uk Kim
-- strict thread matches above, loose matches on Subject: below --
2013-10-02 16:15 Moore, Robert
2013-10-01 22:56 Moore, Robert
2013-10-01 22:42 Zheng, Lv
2013-10-01 18:25 Jung-uk Kim
2013-09-30 22:54 Zheng, Lv
2013-09-30 22:50 Zheng, Lv
2013-09-30 22:28 Zheng, Lv
2013-09-30 17:40 Jung-uk Kim
2013-09-27 16:59 Moore, Robert
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.