You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HOMEBREW_VERSION: 4.4.20
ORIGIN: https://github.com/Homebrew/brew
HEAD: 47ef1a3b0b742a78be35c016df6a0279d6035ebb
Last commit: 11 days ago
Branch: stable
Core tap JSON: 14 Feb 14:35 UTC
Core cask tap JSON: 14 Feb 14:35 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 3.3.7 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.7/bin/ruby
CPU: octa-core 64-bit arm_ibiza
Clang: 16.0.0 build 1600
Git: 2.39.5 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 14.6.1-arm64
CLT: 16.2.0.0.1.1733547573
Xcode: N/A
Rosetta 2: false
What were you trying to do (and why)?
I installed PARI/GP using brew, and there is an odd bug that occurs. If you have code that includes the line "default(parisize, 1G)" (the second input doesn't matter as much, this is just setting how much memory the program has access to), then loading that code from the terminal encounters a problem. This bug does not occur on Linux, and appears to only occur when PARI/GP is built for Mac with clang 16, and not with gcc 14. I was informed that:
"With clang, last_tmp_file (a 64bit pointer) get changed set to 0x00000000FFFFFFFF which is precisely the return value of setjmp (32bit -1) which is very suspicious."
This does not happen if you first open the file and then call read("bug.gp"). Perhaps the package for Homebrew can be recompiled using gcc 14 (assuming this does actually fix the issue)?
What happened (include all command output)?
gp opens, but when you type in commands, the output is not printed. There is no system history either, you cannot reference computed values. If you give a syntax error, then it "fixes" itself, and the loading of the file is skipped.
See attachment for a sample output
What did you expect to happen?
I expected gp to operate normally.
See attachment for normal operation
1. Install PARI/GP:
brew install pari
2. Make a file (anything, I called it "bug.gp") containing one line:
default(parisize, 1G)
3. In that same folder, open PARI/GP and the file with the command
gp bug.gp
4. Run any commands that are valid, e.g. 1+2, 5^2. To "fix" the error, make a syntax error like 15-
The text was updated successfully, but these errors were encountered:
brew doctor
outputVerification
brew doctor
output" above saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
twice and am still able to reproduce my issue.brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.brew config
outputWhat were you trying to do (and why)?
I installed PARI/GP using brew, and there is an odd bug that occurs. If you have code that includes the line "default(parisize, 1G)" (the second input doesn't matter as much, this is just setting how much memory the program has access to), then loading that code from the terminal encounters a problem. This bug does not occur on Linux, and appears to only occur when PARI/GP is built for Mac with clang 16, and not with gcc 14. I was informed that:
"With clang, last_tmp_file (a 64bit pointer) get changed set to 0x00000000FFFFFFFF which is precisely the return value of setjmp (32bit -1) which is very suspicious."
This does not happen if you first open the file and then call read("bug.gp"). Perhaps the package for Homebrew can be recompiled using gcc 14 (assuming this does actually fix the issue)?
What happened (include all command output)?
gp opens, but when you type in commands, the output is not printed. There is no system history either, you cannot reference computed values. If you give a syntax error, then it "fixes" itself, and the loading of the file is skipped.
See attachment for a sample output
What did you expect to happen?
I expected gp to operate normally.
See attachment for normal operation
Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: