Hi Takeshi --
I believe that this is conflicting with the standard module named 'List'
that defines a type named 'list'. I'm also wondering whether you might be
running on a file system that is case-insensitive (like Mac OS X or
Cygwin). In any case, you obviously shouldn't be getting an internal
error.
Would you be willing to file a GitHub issue against this?
https://github.com/chapel-lang/chapel/issues/new
Thanks,
-Brad
On Wed, 22 Mar 2017, Takeshi Yamamoto wrote:
> Hello,
>
> I came across an internal error with the attached
> program (named "list.chpl"). It does essentially
> nothing but prints "hello":
>
> writeln( "hello" );
>
> If I change the file name to "mylist.chpl",
> then the error disappears. So, the problem seems
> coming from its file name (which generates
> a module "list"?)
>
> The error message is as follows (also attached as chpl.errmsg):
>
> -----
> $ chpl list.chpl #<-- compilation
> $ ./a.out
>
> $CHPL_HOME/modules/internal/ChapelDistribution.chpl:123: error:
> illegal use of module 'list'
> $CHPL_HOME/modules/internal/ChapelDistribution.chpl:123: error:
> illegal use of module 'list'
> internal error: EXP3851 chpl Version 1.14.0
>
> Internal errors indicate a bug in the Chapel compiler ("It's us, not you"),
> and we're sorry for the hassle. We would appreciate your reporting this bug
> --
> please see http://chapel.cray.com/bugs.html for instructions. In the
> meantime,
> the filename + line number above may be useful in working around the issue.
>
> -----
>
> I have looked at the above ChapelDistribution.chpl, and
> it imports the module "List". However, it is not clear
> how it conflicts with "list.chpl" (in my local directory).
>
> -----
> Other information is as follows:
>
> OS: Mac El Capitan (10.10) + homebrew
>
> $ chpl --version
> chpl Version 1.14.0
>
> $ /usr/local/Cellar/chapel/1.14.0/libexec/util/printchplenv --anonymize
> CHPL_TARGET_PLATFORM: darwin
> CHPL_TARGET_COMPILER: clang
> CHPL_TARGET_ARCH: native
> CHPL_LOCALE_MODEL: flat
> CHPL_COMM: none
> CHPL_TASKS: qthreads
> CHPL_LAUNCHER: none
> CHPL_TIMERS: generic
> CHPL_UNWIND: none
> CHPL_MEM: jemalloc
> CHPL_MAKE: make
> CHPL_ATOMICS: intrinsics
> CHPL_GMP: none
> CHPL_HWLOC: hwloc
> CHPL_REGEXP: re2
> CHPL_WIDE_POINTERS: struct
> CHPL_AUX_FILESYS: none
>
>
> $ gcc --version
> Configured with:
> --prefix=/Applications/Xcode.app/Contents/Developer/usr
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 8.0.0 (clang-800.0.42.1)
> Target: x86_64-apple-darwin15.6.0
> Thread model: posix
> InstalledDir:
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>
> --- I have also GCC-6 installed via homebrew.
>
> -----
>
> In $CHPL_HOME/STATUS, the following seems possibly
> related, but not sure at all:
>
> - Names in a Chapel program can collide with names used internally.
>
> - User modules named the same as types defined
> internal/standard modules can cause multiple definition errors.
>
> -----
>
> With best regards,
> Takeshi Yamamoto
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Chapel-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-bugs
