9:34 p.m.
* "Adam Rappoport" <arappoport(a)amcc.com>:
Hi!
Is anyone around with verilog background?
Thanks,
norbert.
Hi Norbert -
Yesterday I registered and logged on to xemacs.org and submitted (or so
I thought) a bug report for an issue I am having but when I checked the
open issues list I do not see it. That is okay as I didn't hold out much
hope for resolution.
The problem is most likely trivial and I thought I would shoot you an
email as perhaps you would have a quick idea on how to resolve it.
Basically I am using xemacs, version 21.5 and I am building up a design
for an ASIC coded in verilog. I am using several of the verilog
extensions, AUTOINPUT, AUTOOUTPUT, as well as AUTOINST. I am also using
the AUTO_TEMPLATE for wiring at my top level as top level wiring has
different names then the ports. Anyways I find that at the top level
these autos fail and I get a message, buffer to big as xemacs goes
through the auto sequence. Is there any remedy to this?
Any advice or ideas who I may forward this question to would be helpful.
Adam Rappoport
ASIC Designer - AMCC
--------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and contains information that is confidential and
proprietary to Applied Micro Circuits Corporation or its subsidiaries. It is to be used
solely for the purpose of furthering the parties' business relationship. All
unauthorized review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy all copies of
the original message.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:36 p.m.
New subject: [issue] Bug report does not appear on tracker
Norbert Koch writes:
* "Adam Rappoport" <arappoport(a)amcc.com>:
> Yesterday I registered and logged on to xemacs.org and submitted
(or so
> I thought) a bug report for an issue I am having but when I checked the
> open issues list I do not see it.
I don't see it either.
I would appreciate it if you would resubmit the bug report on the
tracker. My guess is that you filled out the form and got some kind
of error and never resubmitted, but I don't see it in the logs.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:43 p.m.
New subject: verilog mode problem
Norbert Koch writes:
> different names then the ports. Anyways I find that at the top
level
> these autos fail and I get a message, buffer to big as xemacs goes
> through the auto sequence. Is there any remedy to this?
>
> Any advice or ideas who I may forward this question to would be helpful.
>
> Adam Rappoport
Please report the *exact* message in full. This makes it much easier
to identify the code where the failure is occurring (if it's in
XEmacs).
A quick grep through verilog.el gives no hits on "too big". XEmacs
buffers have no size limit (except the amount of virtual memory
available on your system), so it seems likely that this is occuring in
a subprocess (verilog itself?), not in XEmacs.
Please follow up, however. It is possible that XEmacs is configuring
the subprocess with too little memory or something, and that by
changing the configuration of verilog mode this constraint can be
relaxed.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:25 a.m.
New subject: verilog mode problem
Thank you Stephen and Norbert.
I will resubmit the bug with as much detail as possible. I theorized to
a coworker that I believe the problem is more inherent to some system
configuration or limitation on our Unix platform rather then with xemacs
itself.
Adam
-----Original Message-----
From: Stephen J. Turnbull [mailto:stephenï¼ xemacs.org]
Sent: Wednesday, April 23, 2008 3:44 PM
To: Norbert Koch
Cc: xemacs-beta(a)xemacs.org; Adam Rappoport
Subject: verilog mode problem
Norbert Koch writes:
> different names then the ports. Anyways I find that at the top
level > > these autos fail and I get a message, buffer to big as xemacs
goes > > through the auto sequence. Is there any remedy to this?
>
> Any advice or ideas who I may forward this question to would be
helpful.
>
> Adam Rappoport
Please report the *exact* message in full. This makes it much easier to
identify the code where the failure is occurring (if it's in XEmacs).
A quick grep through verilog.el gives no hits on "too big". XEmacs
buffers have no size limit (except the amount of virtual memory
available on your system), so it seems likely that this is occuring in a
subprocess (verilog itself?), not in XEmacs.
Please follow up, however. It is possible that XEmacs is configuring
the subprocess with too little memory or something, and that by changing
the configuration of verilog mode this constraint can be relaxed.
--------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and contains information that is confidential and
proprietary to Applied Micro Circuits Corporation or its subsidiaries. It is to be used
solely for the purpose of furthering the parties' business relationship. All
unauthorized review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy all copies of
the original message.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
1:35 p.m.
New subject: [issue] Bug report does not appear on tracker
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
Norbert Koch writes:
> * "Adam Rappoport" <arappoport(a)amcc.com>:
> > Yesterday I registered and logged on to xemacs.org and submitted (or so
> > I thought) a bug report for an issue I am having but when I checked the
> > open issues list I do not see it.
I don't see it either.
Is this it? http://tracker.xemacs.org/XEmacs/its/issue356
I think that the tracker summaries are not working. I cannot see
issue 209 in either Show Unassigned or Show Open.
--
Pete Forman -./\.- Disclaimer: This post is originated
WesternGeco -./\.- by myself and does not represent
pete.forman(a)westerngeco.com -./\.- the opinion of Schlumberger or
http://petef.22web.net -./\.- WesternGeco.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
7:37 p.m.
New subject: [issue] Bug report does not appear on tracker
Pete Forman writes:
Is this it? http://tracker.xemacs.org/XEmacs/its/issue356
Looks that way.
I think that the tracker summaries are not working. I cannot see
issue 209 in either Show Unassigned or Show Open.
OK, verified. Thanks for the report! These two issues should show up
now. I think I know what the problem is, but can't work on it today.
For future reference, this is issue361.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
3:21 p.m.
New subject: [issue] Bug report does not appear on tracker
At 2008-04-25 03:37 +0900, Stephen J. Turnbull wrote:
Pete Forman writes:
> Is this it? http://tracker.xemacs.org/XEmacs/its/issue356
Looks that way.
> I think that the tracker summaries are not working. I cannot see
> issue 209 in either Show Unassigned or Show Open.
OK, verified. Thanks for the report! These two issues should show up
now. I think I know what the problem is, but can't work on it today.
For future reference, this is issue361.
Issues 361, 356, and 209 are still not showing in the Show Open
summary. I'm hoping that 361 especially has not been forgotten about
as it is masking itself as well as the other open issues.
--
Pete Forman -./\.- Disclaimer: This post is originated
WesternGeco -./\.- by myself and does not represent
pete.forman(a)westerngeco.com -./\.- the opinion of Schlumberger or
http://petef.22web.net -./\.- WesternGeco.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
5817
days inactive
5846
days old
6 comments
4 participants
participants (4)
-
Adam Rappoport -
Norbert Koch -
Pete Forman -
Stephen J. Turnbull